The price comes before the form, not after it
The usual shape of an automation website is a contact form standing between you and any number at all. You describe your problem into a box, and a week later someone calls to qualify you. That arrangement exists to protect the seller's pricing, not to help you.
So the order here is inverted. The plain-English page reads what you typed, names the builds that cover it, and shows the price, the monthly fee, the modelled platform usage and the timeline, before it asks for anything. The manual scope builder does the same arithmetic with no form at all. If you want a number and nothing else, take it and go; that is a legitimate use of this site and no follow-up is triggered.
Why the form asks so much
The form appears only after you have a price, and it is longer than most. That is because everything on the page above it was estimated from a paragraph. A paragraph is enough to name the builds and produce a band. It is not enough to commit to a number.
Each field earns its place by changing the quote or the sequencing. None of it is collected because a CRM has a column for it, and each one shows you why it is being asked while you fill it in:
- Systems it must touch. The single biggest driver of build hours. Two systems with good APIs is a different job from five, one of which is a desktop application with a CSV export.
- How it is done today. Tells us what we are replacing and, more usefully, what breaks. The failure modes of your manual process are the acceptance tests for the automated one.
- What good looks like. This becomes the acceptance test, in your words rather than ours. It is the field that most often changes the scope, because what a client wants is regularly narrower and cheaper than what they described.
- Volumes. Platform usage is billed at cost, so your volumes are the difference between a $30 monthly bill and a $300 one. Guesses are fine; ranges are fine.
- Deadline or trigger. A date changes sequencing and sometimes cost. It is also the honest way to find out that we are the wrong studio because we cannot make it.
- Budget. Not so we can price to it. So we know whether to scope up or down. A client with $4,000 and a $12,000 idea is better served by hearing which third of it to build first.
- Who can grant access, and who signs off. The two most common causes of a stalled build, and both are knowable on day one.
- What rules an approach out. Vendor lock-ins, contracts with time left on them, internal policy. Finding these in week three costs real money.
- Partner token. If someone referred you, their code goes here, and it is how they get paid. It costs you nothing and there is no discount attached, so we are not going to pretend otherwise.
Where it actually goes
The submission is written to our own records first and only then forwarded to the team channel we work out of. That order is deliberate: the chat notification is a convenience, and if it fails the enquiry must still exist. A lead lost to an integration hiccup is a real loss caused by a cosmetic dependency, and it is the kind of failure that never gets noticed because nobody knows the message was supposed to arrive.
The whole scope goes with it, including everything the page calculated, so you never repeat yourself on the call and nobody re-derives your numbers from memory. You get a reference code on screen immediately. Quoting it in any later email means we know exactly which version of which scope you mean.
What we do not do with it
We keep what you send to quote the work and to pay a partner if one referred you. It is not sold, not traded, and not fed into a mailing list you did not ask to be on. There is no drip sequence behind this form. If you send a scope and never hear from us again after the written reply, that is the system working as designed.
The page itself carries no third-party tracking scripts, which is also why the price is computed and shown to you without anything being submitted anywhere.
What comes back
Normally within one business day, a written scope that quotes your reference and contains three things the page could not give you: a firm band rather than an estimate, the assumptions we priced against listed explicitly, and a note on what would change the number in either direction.
If we think you should not buy, the reply says that. If a smaller build would get you most of the benefit, it names the smaller build. If it needs a call we will book one, and if it does not we will say so and save you the hour, which is the part most people are surprised by and the part we would most like to be known for.
If the form is not for you
Email works. So does the phone. The contact page has both, and four lines is genuinely enough to get a price range in the first reply. The form is the thorough option, not the required one.