Tinkerberry Labs
AI automation for construction

Estimates, site reports and scheduling without the evening paperwork.

Estimating takes evenings, site reports are WhatsApp photos, and variations get argued about months later.

Main contractorsSpecialist tradesFacilities managementField service operations

hours to minutes

takeoff and estimate drafting

100%

of site evidence timestamped and searchable

fewer

disputed variations at final account

8

documented automations for this sector

The automations

Where construction teams lose hours, and what replaces it.

Each one is a system we have specified and built before.

01

Estimating and takeoff assistance

The manual process today
Estimators work evenings pricing drawings and specifications by hand.
What we build
Extraction of quantities and specification items from drawings and documents, priced against your rate library into a draft estimate.
Typical impact
More tenders priced per estimator with consistent rates.
Drawing extractionRate libraryEstimating software
02

Site report and diary generation

The manual process today
Site diaries are written from memory, if at all.
What we build
Photos and voice notes from site become structured daily reports with weather, labour, progress and issues, filed automatically.
Typical impact
Complete records that stand up in a dispute.
Mobile captureSpeech + visionProject management tool
03

RFI and submittal management

The manual process today
RFIs sit unanswered and submittals are tracked in a spreadsheet.
What we build
Automatic drafting of RFIs from site queries, routing, chasing and status reporting against contract deadlines.
Typical impact
Response times improve and deadline exposure is visible.
Common data environmentWorkflow automationReporting
04

Variation and claim evidence assembly

The manual process today
Proving a variation months later means digging through emails and photos.
What we build
Continuous linking of instructions, correspondence and site evidence to each variation, with a claim narrative drafted on demand.
Typical impact
Entitlement supported by evidence rather than memory.
Email / photo indexingTimeline buildingDocument generation
05

Health and safety observation triage

The manual process today
Safety observations are logged inconsistently and rarely analysed.
What we build
Photo and voice capture converted into structured observations, risk-ranked, with trend analysis and corrective action tracking.
Typical impact
Leading indicators become visible before an incident.
Mobile captureClassificationH&S dashboard
06

Field scheduling and dispatch

The manual process today
Dispatchers rebuild the day's schedule every time a job overruns.
What we build
Skill, location and SLA aware scheduling with automatic rebooking and customer notification when things change.
Typical impact
More jobs per engineer per day; fewer missed windows.
FSM systemRouting optimisationCustomer messaging
07

Quote follow-up for trades

The manual process today
Quotes are sent and never followed up, so win rates suffer.
What we build
Automated, polite follow-up sequences with objection handling and an option to rebook a site visit.
Typical impact
Win rate improves on follow-up discipline alone.
CRMMessaging automationCalendar booking
08

Subcontractor compliance tracking

The manual process today
Insurance certificates, qualifications and RAMS expire unnoticed.
What we build
Document extraction with expiry tracking, automatic chasing and site-access blocking when a document lapses.
Typical impact
Compliance maintained without a full-time administrator.
Document AIExpiry automationAccess control
Questions

What construction teams ask us.

That is why we build around WhatsApp, voice notes and photos rather than new apps. If a task needs more than thirty seconds on site, adoption fails and we design it out.

PDF and image drawings work well for schedules, specifications and annotated quantities. Full model-based takeoff from IFC or Revit is possible and scoped separately.

Audits are a fixed fee and are credited against a build. Single-workflow builds typically land in the low five figures, multi-workflow programmes higher, and ongoing running and support is a fixed monthly fee. You get the number before we start, not a rolling hourly bill.

A first pilot on your real data usually runs within two to four weeks of the kickoff call. Full deployment with integrations and training normally lands between weeks four and eight.

Your automation plan

Tell us what your construction team keeps doing by hand.

Thirty minutes, no pitch deck. We map the process, tell you whether automation pays back, and give you a rough cost before you commit to anything.

The work
How often does it happen?
Hours it costs your team each week

Three short steps. An engineer reads it and replies, usually within a business day.

Other sectors

Automations for adjacent industries.