Industry

Custom Software for Construction and Trade Businesses

Keep the instruction, site record, agreed variation and job cost connected. We build bespoke software for construction and trade businesses whose office and field teams need a clearer picture of the same work.

From the first instruction to the final invoice

A job can pass through estimators, planners, site teams, subcontractors and accounts before it is complete. If each team keeps its own version of the information, it becomes harder to see what has been agreed, what is outstanding and where costs are changing.

The starting point is your process. A contractor system can connect these stages without forcing every type of work into the same template:

  1. Capture the instruction and scope. Keep the customer, site, survey, photographs and scope together so the team starts with the same information.
  2. Estimate and record approval. Track the proposed work, expected labour and materials, and the version that was approved. Separate an estimate from an instruction to proceed.
  3. Plan people and materials. Allocate work to operatives and subcontractors, record dependencies and make outstanding purchases visible to the people planning the job.
  4. Record what happens on site. Bring hours, progress notes, photographs and material use back to the job record through interfaces designed for the people doing the work.
  5. Control variations. Record the change, supporting evidence, price and approval status. Make work awaiting a decision visible before its cost disappears into the original scope.
  6. Complete and review. Gather completion records, prepare the information needed for invoicing and compare the job's costs with the agreed work.

These are examples of possible scope. We agree the stages, permissions and handovers around your operation before building them.

See what each job is costing

A busy order book does not tell you which jobs are performing well. Job records, labour, purchases, subcontractor costs and reporting are potential requirements to agree, not a feature list delivered for any one client. They need to be connected to the right work, with an agreed way of treating outstanding orders and unapproved variations.

Wider operational requirements may belong in bespoke ERP software. Capturing information on site is covered by mobile app development.

We can build job-costing views around the decisions your team needs to make: where actual costs are moving away from the estimate, which changes need approval and which completed jobs are still waiting to be invoiced.

The definitions matter as much as the dashboard. We establish where each figure comes from and distinguish recorded, committed and estimated costs so a useful comparison is not mistaken for a final profit figure.

An example: insurance reinstatement work

For a reinstatement contractor, an instruction may lead to a site survey, a scope of works, approval, several trades and further variations as the work develops. A connected record can bring those stages together with photographs, correspondence and completion evidence.

The approval steps and reporting would be designed around the parties involved in your jobs. This is an example of a workflow we can discuss, not a claim that every insurer uses the same process or that a particular insurer integration is already available.

Relevant experience in field operations and job costing

Amjutan: connecting the office and the field

BSPOKE developed bespoke desktop and tablet applications for UK water-supply company Amjutan after off-the-shelf software did not meet its requirements. This is a water-supply project, not an insurance-reinstatement case study.

Read the Amjutan case study

Leicester City Council: a dedicated job-costing system

BSPOKE replaced the Highways Department's old Access system with a desktop application covering work orders, labour hours, costs and income. The project shows how software can support the detail of an organisation's work and reporting requirements.

Read the Leicester job-costing case study
Technology

Our technology stack

We select the right technology for your project, not the easiest one for us. Every stack we deploy is modern, well-supported and chosen to give your software a long and maintainable life.

Languages
PHP Python C# / .NET JavaScript TypeScript Swift Kotlin
Frameworks
Laravel React Vue.js Angular Node.js React Native ASP.NET
Databases
MySQL PostgreSQL SQL Server MongoDB SQLite Redis
Cloud and hosting
AWS Microsoft Azure Google Cloud Linux VPS cPanel Docker
AI and integrations
OpenAI API Azure AI Claude API Sage Xero Stripe Microsoft 365 Mailchimp Zapier Fleetmatics
Mobile
iOS (Swift) Android (Kotlin) React Native PWA Offline sync

Connect the tools that already work

You may need one operational system, an application for site teams or an integration between tools you already use. We assess that before recommending a larger replacement.

Explore bespoke ERP software for connected operations, mobile app development for field teams and systems integration for connecting existing platforms. If your main requirement is managing buildings, assets and planned maintenance, see our property and facilities software.

Questions about contractor software

Offline working can be designed for the tasks that need it. We agree what is available on the device, how changes synchronise and how conflicts are handled when a connection returns.

Yes. Access can be scoped to the information and actions each role needs. Permissions, document visibility and approval responsibilities form part of the agreed requirements.

Not necessarily. An integration may allow the operational system and your accounting platform to keep their separate roles. We first check the supported interfaces and the records that need to move between them.

Yes. We can agree an initial priority, such as site records or job costing, and plan how it fits with the wider workflow. Work is prioritised and reviewed through our transparent hourly development model.

Talk us through one typical job

Tell us how work reaches you, how it moves from the office to site and where information is being lost or entered twice. You do not need a finished software specification to start the conversation.