Skip to content
Solutions

Software for a building contractor that you describe in plain words

Describe a building contractor to the BARITA AI crew in plain words and it designs the software for it. Slipping jobs show early, and changes agreed on site end up on a claim.

Where it starts

Run until now from spreadsheets and the site managers' heads. The business in this demonstration: Five to eight jobs at once, from home extensions to small office fit-outs.

This is a product demonstration with a made-up business, not a customer story.

What the app takes care of

  • Each job's schedule, budget, materials and subcontractors lived in different spreadsheets and the site managers' heads. One page per job holds the schedule, the cost against budget line by line, the crews and the latest site report.
  • Cost overruns were found out too late. Every job is rated on track, at risk or slipping against limits the owner sets, with the reason in one sentence.
  • Change requests from clients were agreed on site and never billed. A change is priced and approved on record, then goes onto the next progress claim.
  • Evenings went on chasing daily updates and photos. Site managers file a report with photos from the phone, and the office sees which sites have not reported.
  • It was hard to tell which jobs are on track and which are slipping. Ask which jobs are slipping and what it costs, and the crew answers from the costs, stages and reports.

The screens the crew designed

  • Every job, worst first, for Owner: Which jobs are slipping and why, in one sentence each, with schedule and cost against plan, variations not yet billed and the forecast margin.
  • Why this job is slipping, for Owner and office: The forecast finish against the agreed date, the cost against budget line by line, the stages on a schedule, and what needs doing today.
  • The daily report, from the site, for Site managers: Weather, who was on site, work done, delays with the hours lost and photos, filed from a phone, with a flag when a report is overdue.
  • Every site, every day, for Owner and office: Reports and photos from all sites in one diary, with the sites that have not reported flagged at the top.
  • Changes agreed on site, billed, for Office: Every client change request from the request to the approval on record to the claim it goes on, with the amount approved but not yet billed.
  • Progress claims, for Office: What is outstanding, what has been done but not claimed, and a claim built line by line from the work and the approved variations.

Routines it runs

In this session the crew planned in-app and email notices; phone alerts are not part of this first plan.

  • Variation to claim. When a client approval is recorded for a change: The change is ready to add to the next progress claim for that job at its approved price.
  • Missing report. When an active job has no daily report for more than the days the owner sets: The job is flagged on the portfolio and the site diary as at risk until a report is filed.
  • Job rating. When a cost is recorded or a stage moves: The job is rated again against the limits the owner sets, and the reason is written out.

What changes for the owner

  • Overruns seen as they happen. Each job shows its cost and schedule against plan, so a problem is a Tuesday conversation, not a final-account surprise.
  • Nothing agreed on site goes unbilled. Client changes are priced, approved on record and carried onto the next claim.
  • Evenings back. Site managers file their report and photos from the phone, and the office sees who has not.

Who works on it

Leo, the lead, brought in the experts this job needed: Leo, Archie, Dax, Dez.

Related answers

Tell the crew what your business needs

Describe it in your own words. You approve what goes live.

Get startedAll features