Use the request form at signaliz.com/managed-builds to describe the outcome once, see the matching build lane, and send the brief for review. The form does not collect payment information.
Before you start
Have these details ready:
the outcome your team needs;
the system or file you are starting from;
an approximate number of returned records;
one-time, on-demand, or recurring cadence;
the qualification policy that decides what passes;
where the approved result should go;
any tools, edge cases, examples, or constraints Signaliz should preserve.
If you do not know the right starting point, cadence, or policy, choose the recommendation option. The blueprint review exists to resolve those choices before billing or build work.
Complete the estimate
1. Name the build
Use a name that describes the operating outcome, such as Product expansion account motion or Weekly hiring-signal monitor.
2. Choose the outcome
Available outcomes are:
Build an account list
Find the right person
Enrich a list
Score and qualify leads
Monitor a signal
Prepare a campaign
Build a custom system
3. Choose the starting point
You can start from a verified Signaliz signal, CSV or spreadsheet, your Clay workspace, your CRM, an API or webhook, or a request for a recommendation.
4. Choose the cadence and volume
Choose one-time, on-demand, daily, weekly, monthly, or recommendation. Enter an expected returned-record count from 1 to 100,000.
Volume changes the architecture at 250 and 2,500 returned records because larger jobs need batch QA, exception handling, and delivery controls. Managed builds are priced for implementation depth and operating capacity, not as a commodity price per row.
5. Set the qualification policy
Choose the closest policy or ask Signaliz to recommend one. If your policy is documented elsewhere, choose Use my uploaded policy and attach it or explain it in the notes.
6. Choose delivery
Select one or more of:
Workspace — private Signaliz workspace;
CSV — clean reviewed download;
Webhook — programmatic trigger and returned result;
API — call the delivered system over REST;
MCP — run it from a supported AI client;
CLI — operate it from the command line.
Programmatic delivery requires connection and permission QA, so it routes to at least a Connected Build.
Add contact details and an optional brief
Enter the name, work email, and company that should receive the blueprint. Signaliz uses this information to review and reply to the request.
You may attach one PDF, DOCX, CSV, or XLSX file up to 10 MB. Do not include passwords, API keys, private keyed MCP URLs, or other secrets. Access is provisioned separately after scope and permission review.
Use the notes for tools, failure cases, must-have rules, prohibited actions, and what is not working today.
Review the live estimate
The summary shows:
the estimated build lane and starting price;
one-time or monthly billing;
selected delivery methods;
$0payment today;the specific rules that caused the routing decision.
The server recalculates the estimate when you submit. If the pricing rules changed while the form was open, the request stops and asks you to review the updated estimate. It does not silently create a higher-priced order.
After you submit
A successful request returns an ORD-... ID, stores the brief, and sends a receipt to the work email. The receipt confirms the estimated lane, price, and next step.
What happens next:
Signaliz reviews the outcome, access requirements, assumptions, and estimate.
You receive the exact blueprint, timeline, deliverables, and approved price.
You approve the blueprint and price.
Stripe emails an invoice only after that approval.
Submitting an estimate is not checkout, payment, build completion, or permission to connect to your systems.
If the page says the request was saved but delivery needs review, do not submit it again. Keep the displayed ORD-... ID and contact support so the original request and email receipt can be recovered.
Next: Understand pricing, blueprints, and invoices.