Example scenario
A partial payment is missing from the job view
A service business keeps quotes, job progress and payments in separate files. When a job is partly paid, the team has to open several records to find the outstanding balance.
How would we approach it?
We connect the quote and resulting job to one customer record. Once a partial payment is recorded, the dashboard shows the outstanding amount and finance can export the records for a selected period.
Start with one operational problem
When the same customer is listed in several spreadsheets, staff may spend time reconciling names, quotes and payments. A different team might already have a system for invoices but still track jobs in a notebook. We walk through a representative day with the people who do the work to see where information is entered, checked and handed over.
The first version can focus on one complete process. For example, record a quote, turn the approved quote into a job, record a partial collection and show the balance outstanding. This gives the team something concrete to test before committing to extra screens and reports.
Define what the finance dashboard needs to show
For day-to-day operations, a dashboard can show customer balances, payment schedules, expense categories and a simple cash view. We agree the source for each figure and what staff should do when a payment is disputed or posted to the wrong account. A manager should be able to see why a total changed, and the people maintaining records should understand how to correct them.
If the process depends on statutory accounting, electronic documents or a specific accounting platform, we define the boundary with your accountant and provider. The interface should make clear where internal records end, where formal records live and which data flows between them.
Set permissions and plan the data move
The sales team may create quotes, finance staff may record collections, and a manager may review totals. We agree roles against your real tasks and identify changes that need an approval or history. A first acceptance test can include creating a record as a salesperson, reviewing it as a manager and recording payment as finance.
When data needs to move from spreadsheets or another service, we review a small sample first. We check duplicates, column meanings and totals before proposing a full import. The planned handover covers exports, backups, documentation and who is responsible for maintenance after launch.
Build around staff who will use it
The proposal defines the first workflow, the reports it depends on and the devices staff use. Before expanding, we run through the work on desktop and mobile with examples from the team. Once that first release is usable, we can prioritise additional reports, job stages or integrations according to what staff need next.
Questions before you start
When does custom development make sense over an off-the-shelf tool?
If your existing tool handles most work, start by identifying the missing step. If your team retypes every approved quote into a work order, a small integration or dashboard may be enough. Custom development makes more sense when standard tools cannot support your roles, business rules or reporting needs.
What records can a simple finance module handle?
It can cover account balances, receivable reminders, partial receipts, expense categories and a cash view, depending on scope. Records can link to quotes and work orders. Statutory accounting or electronic invoicing requires a separate discussion with your existing provider about data and responsibilities.
Can we migrate Excel records with their outstanding balances?
We review columns, duplicates and your definition of an outstanding balance first. A trial import can use a sample file. The team checks record counts and balance totals against the original spreadsheet and decides what to do with rows that do not match.
Can staff have different permissions for receipts and pricing?
Roles can follow the workflow. For example, quote staff see the sales status, finance can record receipts, and managers see totals. We test which roles can edit a record and which changes need to be recorded before handover.
How will we know the first version is ready to hand over?
We agree an end-to-end example at the start. For instance, a quote becomes a work order when approved, and a partial receipt updates the remaining balance. The scope records that workflow alongside roles, data export and maintenance responsibilities.