Cadence by Gaidant - Site management platform

The AI that runs the job with you.

Cadence is an AI-native site management platform for the people who actually build things - tradespeople, engineers, project managers. Capture however the moment lets you - a photo, a voice note, a typed line, or all three - and Cadence handles the records, the reporting and the chasing on every job.

NEW CAPTURECadence · Level 7 eastClassifyingCAPTUREPhoto · 12:430:08TPhoto · Voice · Text4 tags attachedFANNING OUT TOSafetyGuardrail missing at level-7 east edgeAwaiting confirmation · high priority0.95QualityColumn finish inspection - pending sign-offAttached to drawing S-207 rev C0.82ProgressLevel 7 pour milestone reachedAdvances schedule item P-14 by 1 day0.91Each record carries its own audit historyVerify to close

The difference

What makes Cadence different.

Built as an agent, not a feature.

Most construction platforms were built around fixed workflows, with AI bolted on later to automate the gaps. Cadence starts the other way around. The agent is the substrate - the records, the reports, the chasing, the translation work all sit on top of it - so the help shows up in the work itself, not in a side panel you have to remember to open.

It learns the job from you, not the other way around.

Conditional-workflow tools ask you to define how a project should run before it starts. Real projects don't work like that - they form as the job meets reality. Cadence picks up how you already file your daily log, which fields your client actually reads, which subs need chasing twice, and the templates you reuse on every report.

One capture, every record it touches.

Snap a photo, dictate a voice note, type a line, or do all three - whatever the moment calls for. Cadence reads the context and fans the capture out into the safety record, the quality record, the progress record, and the daily log, each with its own audit history. You write the thing once; it becomes the seven things the general contractor, the safety officer, the engineer of record and the client each need it to be.

Your voice is preserved, not flattened.

The reports read like you wrote them, because you did. Cadence handles the format translation between how the site actually runs and how each stakeholder wants the paperwork to look. Templates you configure once are reused on every job, and every AI-classified record is provisional until a verified user confirms it.

For the people on the job

A partner for whoever runs the job.

We try not to throw the word partner around the way software companies do. What we mean is specific. A good apprentice on a site doesn't ask you to change how you work - they learn how you work, then make themselves useful inside it. They pick up that you write your daily logs in shorthand and tidy them at the truck. They notice that when you say tell the client we're on track, you mean a particular kind of email with a particular tone. They catch the small handoffs before they become problems.

That is what Cadence is built to do, and it works the same way whether you're a foreman, an engineer or a PM. For the foreman, it turns the photo and the voice note into the daily log, the incident form and the toolbox-talk record - in the shorthand you already use. For the engineer, it drafts the RFI in the language your engineer-of-record will actually read, holds the spec in memory, and chases the answer. For the PM, it re-formats the same incident into the three different templates your general contractor, your safety officer and your client each require, catches the handoffs and keeps the audit trail clean.

None of this asks you to learn a new system, fill in a new template, or change the way you talk to your crew. The software adapts. You don't.

What that looks like, concretely

  • ·Daily logs written in your shorthand, cleaned up for the client without losing your voice.
  • ·The same incident re-formatted into the three templates the general contractor, the safety officer and the owner each want.
  • ·RFIs drafted in the language your engineer-of-record will actually read, chased until the answer comes back.
  • ·Templates and taxonomies you configure once, reused on every project - the system files the way your team files.

The thesis

Chaos is the feature, not the bug.

McKinsey calls every construction project a one-off prototype. They mean it as a critique - proof of why the industry is hard to digitise. We think they have it backwards.

The variability of construction isn't a defect in the industry. It is the industry. No two sites are the same. No two crews work the same way. No two PMs run a job the same way, even inside the same company. The drawings change because the building is being made for the first time. The schedule changes because weather, inspectors, subs and material lead times are not pretending to be predictable. The reporting changes because every client wants something slightly different and every authority wants something slightly different again. This isn't chaos to be eliminated. It is judgment under variable conditions, which is what skilled trades, skilled engineering and skilled project management have always actually been.

The mistake most construction software makes is to treat that variability as the problem to solve. The result is software that works beautifully in the brochure and gets quietly abandoned on site, because the moment the project does what projects do - change - the software is in the way. Cadence is built on the opposite bet. The chaos stays. It's the only honest thing on a job site. What goes is the administrative tax that gets paid every time the project shifts.

How it works

What Cadence does on the job.

Capture however the moment lets you - a photo from the deck, a voice note on the way back to the truck, a typed line, or any combination. Cadence reads the context of what's on the screen and what's on the site, classifies the capture, and fans it out into structured safety, quality and progress records, each with its own audit history. A verified user confirms or amends every record, and every change is captured in a signed-style audit trail.

TPhoto·Voice·TextCaptureHowever the moment lets youReads contextClassifyAI infers what was capturedSafety·Quality·ProgressFan outOne capture, every record it touchesVerified·AuditableConfirmHuman-in-the-loop with audit history

Reports and Excel exports use templates you configure once and reuse on every job. Drawings live in the workspace with pin-to-location markup. Each project carries its own taxonomy, its own field labels and its own reporting voice - and the agent picks those up from how you actually work, not from a setup wizard.

It runs on AWS with per-tenant isolation. Vision and text classification are powered by Claude on Amazon Bedrock; no model keys leave the cloud. Designed for CCTV and IoT inputs via webhook and API when a project elects to wire them in.

Photo, voice, typed note, or any combination - classified and fanned out across safety, quality and progress
Signed-style audit trail on every record - verified user, original AI classification, every status change
Multi-project workspace with drawings and pin-to-location
Adaptive report and Excel templates that reuse your taxonomy on every job
Connector-agnostic API integrations with the building software you already use
Custom skills and tools that extend the agent with project-specific actions
Runs as managed SaaS on our AWS, or deploys into your cloud via Terraform
Per-tenant isolation with Claude on Bedrock for vision and text classification
Structured to accept CCTV and IoT feeds when a project chooses to integrate

Fits into the stack you already run

Connector-agnostic. Extensible by design.

{ }QP checklist{ }Insurer escalation{ }Custom exportProject managementDocument controlScheduling & planningDrawings & BIMERP & financeField & safety appsYour internal APIsCadenceCustom skills extend the agent with project-specific actions

Integrates with the building software you already use.

If your team is on a project-management platform, a document-control system, a scheduler, a drawings or BIM tool, an ERP, or a field/safety app - or anything else that exposes an API your team is licensed for - Cadence can talk to it. The integration layer is connector-agnostic. We don't care which platform you're standardised on; we care that the agent has the context to be useful.

Once wired in, the integration becomes additional context for the agent. It can pull the right RFI thread before drafting a reply, reference the drawing version your engineer is working from, or post a daily log back into your system of record - without you switching tabs.

Custom skills, built for your projects.

Every project has its own quirks - a checklist your QP requires, an escalation path your insurer wants, an export format your client's finance team insists on. Cadence supports custom skills and tools that extend the agent with project-specific actions, so the work you used to track in a spreadsheet becomes something the agent can actually do.

Skills are configurable by us during onboarding and can be expanded as the project teaches you what it needs. The agent inherits them as soon as they're defined - no separate launch, no new app to install.

Where it runs

Runs where you want it to run.

Two deployment modes, same product. Pick the one that fits your team's constraints on data, sovereignty and operational overhead.

Option AFastest to start

Managed SaaS.

Cadence hosted by us. Zero infrastructure for you to run, no engineers to hire on day one, no cloud bill to argue with. New projects onboard in days rather than quarters.

Runs on our AWS with per-tenant isolation - your project's data, records, drawings and audit history live in a partition scoped to your organisation. Updates ship continuously; you get them the day they're ready.

Option BYour cloud, your control

Deploy in your own cloud.

We ship the full Cadence stack as Terraform your platform team can apply in your AWS account. Your data never leaves your perimeter; your compliance boundary stays exactly where your auditors already understand it.

Right for teams with strict data-residency, regulator, or IP requirements - or clients who've already made a "our-cloud, always" policy call. AWS today; Azure and GCP available on request. Updates ship as versioned modules you promote on your own release cadence.

Built where the standards are

Built for Singapore, shaped for anywhere.

Cadence is designed around the three-tier site management model - Basic, Intermediate, Advanced - described in the BCA Site Management Platform guidebook, so Singapore teams can adopt at the maturity level that fits the project. The data model is structured for SGBuildex data exchange when a project elects to integrate; live integration requires SIT/UAT against your project instance. The platform itself is region-agnostic and works the same way on sites outside Singapore.

See it run on your next capture.

Try Cadence on a real one - a drawing, a daily log, or an incident from a live project. We'll show you Cadence working on it, not a deck about it.