Find out exactly what a system would take, before you commit to building one.
A fixed-price audit of how the work runs today, written up as a specification you keep: what to build, in what phases, by when and for roughly how much. If you go ahead, the fee is credited toward the build.
Worth it when the scope is not obvious.
- A process you already know is costing time — and you want to know what fixing it would take before you commit to a build.
- More than one person, tool or location is involved, so the answer is not obvious from one conversation.
- You need a document you can take to a partner, a board or a budget meeting.
Not every project needs one.
- Small, well-defined work — one integration, one automated report. That can usually go straight to a written proposal, with no audit.
- A general IT health check. The audit is about how work moves through the business, not the state of the network.
- Choosing between two off-the-shelf products you have already shortlisted. A demo from each vendor will answer that faster.
A specification you can act on.
Everything a build would need decided, written down, and yours to keep.
- Workflow mapping
- Requirements
- User roles and permissions
- Integrations
- Technical architecture
- UX planning
- Scope and project phases
- Estimated timeline
- Budget
- An estimate of the hours and dollars your current workarounds cost per year
- A written specification you keep
You keep the specification whether or not I build it.
Fixed fee, agreed before it starts
Credited toward the build if you go ahead.
A written proposal
Every build is quoted against a written scope. The approved figure is the figure you pay.
About the workflow audit.
What is a workflow audit?
A fixed-price piece of paid discovery. I map how the work actually runs today, find where the time and errors go, and write up what a system would have to do — who uses it, what it connects to, in what phases — with a timeline and a budget. It answers “what would this take?” before you commit to building anything.
How much does it cost?
It is a fixed fee, agreed before it starts and quoted from the first conversation, so there is no meter running. If you go ahead with the build, the fee is credited toward it.
What if I decide not to build?
You keep the specification whether or not I build it. It is written to be useful on its own: you can take it to another developer, use it to choose a product, or put it in a drawer until the budget is there.
How long does it take?
It depends on how many people and systems are involved; the timeline is agreed before it starts, along with the fee.
Do I need one?
Not always. If the free conversation shows the work is small and well defined, it can go straight to a written proposal. The audit is for larger or less certain projects, where guessing the scope would cost more than finding it out.
Start with the free conversation.
About 30 minutes. If an audit is the right next step, I’ll say so and quote it; if the work is small enough to propose straight away, I’ll say that instead. You work with Mina throughout.
You’ll hear directly from PiTech, typically the same business day.