Managed-build pricing follows implementation depth, operating scale, customer-system access, delivery interfaces, and cadence. The request form gives a rules-based starting estimate; the blueprint confirms the exact scope and price before any invoice.
Prices below were verified on August 3, 2026. Use the live estimator for the current amount.
Lane | Current starting price | Best fit | Included capacity |
Focused Build | $499 one time | One focused Clay outcome | Outcome/input diagnosis, focused workflow, QA contract, reusable Signaliz runbook |
Complex Build | $999 one time | Branching or multi-step logic without integrations | Net-new architecture, evidence gates, two QA cycles, reusable result surface |
Connected Build | $2,499 one time | API, MCP, CLI, webhook, CRM, or customer-system access | Permission design, up to 8 build hours, connection QA, rollback plan |
Managed GTM Studio | $4,999/month | Recurring complex or agentic systems | 20 build hours per month, integrations, complete GTM motions, shared backlog and QA |
Embedded GTM Engineering | $9,999/month | Recurring multi-system deployment and operating support | 40 build hours, backend deployment, build-in-your-Clay option, full-motion architecture, operating handoff |
What changes the estimate
The estimator promotes a request when the work requires more architecture or operating capacity:
scoring, qualification, campaign preparation, and custom systems require complex branching or QA;
more than 250 returned records require batch QA and exception handling;
more than 2,500 returned records require scaled execution and delivery controls;
starting from Clay, a CRM, API, or webhook requires access and connection QA;
webhook, API, MCP, or CLI delivery requires a Connected Build;
daily, weekly, or monthly operation uses managed monthly capacity;
recurring work that also combines large volume, multiple live interfaces, customer-system access, or a custom system can require Embedded GTM Engineering.
Expected record count helps size the system, but Signaliz does not price a managed build as a simple per-row purchase.
The blueprint is the approval contract
Before an invoice, the blueprint should identify:
the outcome and success criteria;
accepted inputs and returned outputs;
qualification, evidence, and exception rules;
systems, permissions, and delivery interfaces;
review gates and prohibited actions;
QA method and acceptance checks;
timeline, deliverables, and exact price;
one-time or monthly capacity;
what is out of scope.
If the blueprint changes the lane, price, or material scope, review and accept the new version before an order or invoice proceeds.
Invoice sequence
The request form shows
$0due and collects no payment information.Signaliz reviews the request and returns the blueprint.
You approve the blueprint and exact price.
Stripe emails the invoice.
Payment state is tracked separately from build progress.
An ORD-... request receipt proves the request was stored. It does not prove that an invoice was sent or paid. A Stripe invoice proves billing state. It does not prove the workflow passed QA or reached Final Build.
Build price versus run price
The build price pays for implementation and managed engineering capacity. After delivery, a reusable build can also have a fixed Signaliz-credit price per run. That run price is published in the Final Build contract and is derived from the measured Clay-credit budget for the delivered routine.
Always inspect the delivered build before a run. The build contract shows both:
clay_credits_budget_per_run— the measured execution budget;fixed_credits_per_run— the fixed Signaliz credits charged for an intended live run.
Self-service Signaliz plan entitlements and purchased credits are separate from the implementation invoice. Check the active workspace Billing screen for the current credit balance and plan.
Next: Follow the lifecycle and approval gates.