Every proposal says yes
A supplier quotes what you asked for. Nobody checks whether the ask was the right one, so the price is accurate and the plan is wrong.
Services
Technical consulting
The proposal is on the table, the price is clear, and nobody can say which lines are necessary. Or the team agrees the current system is failing and disagrees on what replaces it. We read the work, the numbers and the constraints, then put the answer in writing: what to build first, what to wait on, what the first release should cost, and who owns each decision while it is being built. Sometimes that document says the thing you asked for is not the thing to build.
Who it is for
- Owners holding a quote they cannot evaluate, from a supplier they have not worked with.
- Teams where sales, finance and the warehouse each want a different system.
- A business about to start a build with nobody responsible for the order of the work.
Problems it solves
The order is decided by seniority
The department with the loudest sponsor goes first and the integration goes last. The pieces arrive and do not meet.
Decisions are not written down
A meeting settles a question, nobody records it, and three months later two people remember different answers. The work is redone, and the second version is not better.
Use cases
A written build order
Which workflow goes first, which waits, which is deliberately out of the first release — one page the whole team can read, with the reason beside each line.
A scope note per release
What is included, what is excluded, and what a change costs. The exclusions matter more: they are where the arguments start in month three.
Running the technical project
Sequencing, a decision log with a date and a name against each entry, and a written status to the person paying — weekly, in plain language, not a chart nobody reads.
Handover and training
Before we leave: sessions with the people who will use the system, on their own data and their own workflows, plus a written procedure for the steps they do once a month.
What is in scope
Fixed scope. Fixed price.
Agreed in writing before anything is built. You approve before we start.
- Sessions with the people who do the work now, and with whoever signs off
- A written build order: what comes first, what waits, what is not being built
- A cost range with its assumptions stated, and what would change it
- A line-by-line review of a quote, or of a system you already own
- Running the project when it starts: sequencing, the decision log, written status
- Training at handover, on your data, with a written procedure for the rare tasks
How it is delivered
- 01
Sit with the work
Half a day at the counter, in the warehouse or with the accountant. We watch the steps that are in no document, because that is where the cost is.
- 02
Try the cheap answer first
Before proposing a build, we check whether a report, a rule or a change to the process removes the problem. It often does, and that answer is cheaper for you and less interesting for us.
- 03
Write it down and price it
A document with the build order, the exclusions, a cost range and the assumptions behind it. You can take it to another supplier; nothing in it depends on us doing the build.
- 04
Run it or hand it over
If we run the project, the decision log and the weekly note are part of the job. If someone else builds it, the document is written so they can start without a meeting with us.
FAQ
Questions about this service.
What owners usually ask before requesting a quote for it.
What do we get at the end?
A written build order, a scope note with its exclusions, and a cost range with its assumptions. Plus the project running and the team trained, if you want those from us.
What if we have already started?
We read what exists before writing anything: the code, the quote, the plan. Sometimes the order is wrong and the work is not wasted; sometimes the foundation is wrong and the honest answer costs money. We will say which one it is.
What if you tell us not to build it?
Then the document says so, with the reason and with what would have to change for the build to make sense. We would rather lose the build than start it on an assumption that fails in month four.
Can you work with our own developer or supplier?
Yes. The document is written for the person who will execute it, not for a drawer. If we also run the project, that is stated separately, so you can compare the two.
Start a project
Want this scoped for your business?
Send the brief. It comes back as a written scope and a fixed quote before anything is built.