One job, then the ones that were not named.
The assessment is the company record. The build is a catalogue solution on your own accounts. Running it afterwards is a decision, not a default.
We learn the company before we choose a tool
This is the workflow assessment. It is a form, and it is also the lesson.
The company record asks who the business is, where you heard of us, the public pages, the tools you already pay for, who does the repeated work today, what you want back in the next 90 days and the next year, and which of the unnamed jobs are already handled, still done by hand, or not yet seen.
It asks how much of the work should run without a person, and it asks what must never be automated. That second answer is a limit, not a field we talk you out of.
You can leave and come back. Sending the record puts it in the review queue. The confirmation is the reference on the screen. We do not email it. Nothing is billed from Plan, and a status of Quoted is a conversation, not a charge.
One job, on the systems you already have
Build and integration means a catalogue build, configured, not a blank file and a new login.
OpenHandoff is one solution from the catalogue, on your numbers, your sender identity, and your wording, with consent and opt-out wired in where the channel needs them. You get a handover document and a 30-day fix warranty. The price on the pricing page is the published band, with a tilde in front because a firm number waits on your volumes.
The scope builder is how you see that band before you talk to us. You can take the number to someone else. We would rather you could.
It does not touch a customer until the proof is the point
Training is the handover, not a slide deck.
A single handoff includes the document that says what was built, what it will not do, and what to do when it breaks. Alerting on that tier fires to you.
Enterprise is the agreement for several systems and one roadmap: a staging environment, source control, rollback, and a named contact. It has no dollar amount on the pricing page on purpose. The number is part of the written agreement, not a band we pretend is universal.
We do not cut a live customer flow over because a demo looked finished. Where the build records calls or sends messages, the sign-off is on the real cases you care about.
Running it is a separate decision
OpenManaged is the month-to-month share, and it is optional.
Monitoring, alerting, incident response, copy and flow changes on request, carrier and deliverability upkeep, and a monthly report. Platform usage is billed at cost and itemised. That is the published shape of the tier. It is not included in a one-off build unless the written agreement says so.
You can also keep the handover and run it yourself. The monthly exists for the company that does not want to think about it, not as a toll on something you already own.
What we will not start on our own
An account is not an instruction to act.
Opening the account does not ask for a card. Sending the company record does not start a job. Adding a build to Plan does not reserve a week of ours.
We will not automate a step you marked as never to be automated, and we will not turn on sending, publishing, or spending because a form was filled in. Those start only in the written agreement for that job, with the review point named.
Start with the record, not a scoping call.
Thirty minutes is sometimes useful later. It is not the price of finding out who you are.
The short version
The long version is above. These are the lines people look for.
Does the company form cost anything?
No. Sending it does not email you and does not create a charge.
Is a quoted reply an invoice?
No. Quoted means we have written back. A bill exists only in a separate written agreement.
Can we start with one job?
Yes. That is OpenHandoff. The company record is still worth filling, because the second job is usually the one nobody had named.