Quoting & calculations
Forms and calculations that follow the rules your business uses.
Internal business tools
Build around the way your team actually works.
When the work lives across spreadsheets, inboxes and separate tools, even a simple task can take too many steps. Give your team a clear place to manage it, with software shaped around the process.
Show us how the task works today. We’ll follow up by email.
You know the job. Your tools make it harder.
An internal tool can help when the same process runs repeatedly and your team has to work around the software to finish it.
- Preparing a quote means copying information across several files or systems.
- Requests and approvals get lost between inboxes, spreadsheets and conversations.
- Staff need a shared view of jobs, customers or records that your current tools do not provide.
Example workflow · tailored to your business
From an incoming request to a reviewed quote.
This illustrates one possible workflow. Start with the process your team uses, including the exceptions, and decide where a custom tool would help.
Capture the request
Collect the customer, job details and information needed to begin.
Prepare the quote
Bring the agreed pricing rules and items into one workspace.
Review & approve
Let the right person check the details before the next step.
Track what happens next
Keep the quote and its status with the customer or job record.
A useful tool starts with a useful workflow.
The features follow the task. Existing tools and their built-in options are reviewed before deciding what needs to be custom.
Requests & approvals
Clear steps, responsibilities and status for recurring work.
Records & dashboards
A shared view of the customers, jobs or information your team needs.
Connections between tools
Move agreed information between systems where their integration options allow it.
Choose one process worth improving first.
Build a complete, useful first version around one task. Work with us to understand the inputs, decisions and exceptions before expanding to other parts of the business.
Walk through today’s process
Show the files, people and steps involved. Identify what already works and where the friction is.
Try it with realistic examples
Review working versions with the people who use the process and check calculations, permissions and exceptions.
Plan the transition
Agree how existing data, team access, launch and handover will be handled before the tool goes into use.
Before you start.
Should we use an existing product instead?
That is checked first. If a setting, integration or existing product meets the need, it may be the simpler approach. A custom tool makes sense when the workflow has requirements those options do not meet.
Can we start from our spreadsheet?
Yes. The spreadsheet can help explain the information, calculations and decisions involved. Its formulas, data quality and exceptions are reviewed before deciding what the tool needs to reproduce or improve.
Can it work with software we already use?
Often, yes. Available integrations, permissions and third-party costs are checked as part of the scope. The proposal explains which information can move between systems and what still needs a manual step.
How does our team move to the new tool?
The launch plan can include data migration, team accounts and a walkthrough. What is included depends on the existing data and the people using the tool; those details are agreed before the build is committed.
How are the budget and ongoing costs decided?
The workflow, user roles, calculation rules, integrations and data migration determine the work. The proposal also covers the agreed hosting, handover and support arrangement, including third-party costs identified during scoping.
Which task takes more work than it should?
Tell us what your team does, which tools are involved and where things get awkward. One concrete example gives us a useful starting point.
Discuss your workflow
A description of the current process is enough to start.