A Small Automation Firm or a Large Consultancy
The difference is not size or price. It is who carries the scoping decision, who writes the code, and what you hold afterwards.
The framing that hides the difference
Small versus large is usually presented as cheap against safe. It is a comfortable way to describe the choice and it explains almost nothing, because the two options differ on things that have no price on them.
Who carries the scoping decision
This is the one that matters most and gets asked least.
In a large firm, the people who gather your operational detail, the people who price the work, and the people who build it are frequently three groups. Detail is lost at each handoff, and the scope that survives is the one that fits the commercial shape of the engagement.
In a small firm they are usually the same person, which removes the losses and concentrates the risk. Either way, the decision about what is worth building should sit with you rather than with the party whose income scales with it - the structural point made in an agency or a freelancer applies here in a larger size.
Who is in the room
Ask directly whether the people presenting will be the people delivering, and ask for names. The answer is not a scandal either way; it is information. A firm that staffs a proposal team and a delivery team can say so and explain how detail is carried across. One that cannot answer has told you what happens after signature.
What the smallest useful piece looks like
Every firm has a floor. A large one's floor is set by its cost structure and is usually well above the cost of automating a single process. Approach it with one process and the scope grows to reach the floor - not out of dishonesty, but out of arithmetic.
That is the practical reason a single-process buyer is better served by whoever can take a single process. It is also why what to automate first is a question with a real answer for a small firm and an awkward one for a large program.
What you hold afterwards
Code, credentials, documentation written for an owner, and a named person on your side who has opinions about the design. This is where a small firm's concentration of knowledge either becomes a risk or stops being one, and the difference is entirely in whether the handover was treated as a stage or as an afternoon.
The order to decide in
Scoping, then people, then floor, then ownership. Price fifth, and only once both totals include twelve months of running alongside the build - which is the arithmetic in how to read an automation quote. Anything settled before those four are answered is settled on the brand, and the brand is not the thing that will be building your process.
01Is a large consultancy safer?+
It is more continuous, which is a different property. If somebody leaves, there is a bench; if the engagement runs for years, there is a firm that will still exist. That is worth paying for on long programs. What it does not buy is a better decision about which of your processes to automate first, because that decision depends on your operational detail, and the people who gathered that detail are frequently not the people who priced the work or the people who will build it.
02Where does a small firm actually lose?+
On continuity and on breadth. One or two people who understand your process deeply are a risk concentrated in one or two people, and the honest answer to that is the handover: documentation written for an owner, a named person on your side, and code you hold. A small firm also cannot staff five workstreams at once, so a program that genuinely needs that is the wrong fit, and saying so is part of what a good one does.
03How does engagement size decide this?+
A large firm has a floor below which it cannot engage profitably, and that floor is usually well above the cost of automating one process. When a buyer with one process approaches a firm whose smallest sensible engagement is a program, the scope grows to meet the floor rather than to meet the problem. That is not dishonesty; it is arithmetic. It is also why the first question worth asking either party is what the smallest useful piece of work they would accept looks like.
04What should the decision actually turn on?+
Four things, in order: who carries the scoping decision, whether the people who priced the work will be the people doing it, what the smallest useful engagement is, and what you hold on the day the relationship ends. Price comes fifth, and only after the totals have been made comparable by putting build and twelve months of running side by side. Anything decided before those four are answered is decided on brand.
Discovery Sprint
If that argument holds for your operation, the next step is measuring it. Thirty minutes on one process, and we say whether the arithmetic is likely to close.
Put a time in the calendarThirty minutes, free. The sprint is what the call is about.
- Fee
- $2,500
- Length
- 1-2 weeks
Refunded in full if we conclude you should not build.
