A focused build without enterprise-level overhead
The exact investment depends on the workflow, the logic behind it, and what the finished tool needs to do. I review the process first, then recommend a focused scope and fixed project quote.
No giant software engagement required. If the workflow is focused and the logic is clear, we can start with the smallest useful version and build only what the process actually needs.
Your workflow does.
Two tools can look equally simple on-screen and require very different work behind the scenes. I quote based on the actual process rather than forcing every project into the same package.
Scope first. Price second.
The goal is to give you a clear project fee before the build begins. You should know what is being built, what counts as done, and what you are paying for.
Show me the process
Use the project form to explain what your team does today, what makes it painful, and what you wish worked differently.
I map the build
I look at the rules, calculations, users, outputs, exceptions, and technical requirements needed for a useful first version.
You get the quote
If it is a fit, I’ll come back with the recommended scope, project fee, and expected timeline before anything starts.
Support without an expensive retainer.
You do not need to keep paying for ongoing support if you do not need it. For tools that do need occasional attention, lightweight monthly and hourly Care options are available at minimum cost.
Enough information to know whether it’s worth asking.
How much does a project cost?
Smaller, clearly defined projects can start around $500. Beyond that, the quote depends on the complexity of the workflow, rules, users, outputs, and technical setup. Submit the project form and I’ll price the actual build rather than giving you a generic package.
Why don’t you publish full price packages?
Because the visible size of a tool is not a reliable measure of the work behind it. A small interface can contain complicated business logic, while a larger-looking tool can sometimes be straightforward. I would rather scope the workflow properly and give you a relevant number.
Do you charge hourly for builds?
Usually no. New builds are generally scoped as a fixed project so we can agree on the outcome and fee before work begins. Hourly pricing is available for suitable post-launch Care work.
Are Care plans required?
No. Once the agreed project is complete, ongoing support is optional. Monthly and hourly Care options are available at minimum cost if you want help with future refinements or maintenance.
What happens if the scope changes?
If a request falls outside what we originally agreed to build, I’ll flag it before doing the work. We can adjust the scope, quote the addition separately, or save it for a later phase.