Transformation happens inside the operation.
We work with your leadership and the people doing the job — following real decisions, agreeing what should change, building it into the day, and staying while your team takes it on.
Ways to work together.
Three routes, and Identify on its own when what should change is not yet settled. Which fits depends on how well the problem is already understood; the capability engagement is one route, not a step you have to take first.
Capability engagement
A fixed-fee, four-week engagement that installs a shared AI environment, standards and reusable prompts across your teams, and ends in a decision about what to build. Every function gets working sessions on its real jobs, and the readout ends with a build, buy, wait or skip call on each candidate. Nothing is deployed, and nothing has to follow it.
Implementation engagement
A console, workflows, a grounded assistant and a governed data layer, implemented inside your business. It is obtained this way and no other: an implementation engagement, scoped in writing, running in your environment on your systems of record. Operating design, integration, workflow definition and adoption are part of the scope, because they are how the platform becomes useful in one particular business.
Continuing operating partnership
Bedrock stays alongside as the work and the tools change, revising what each system is allowed to do with your people approving every change. Handover is paced to the team, with what has been handed over stated plainly, and it is priced the same way as everything else.
Discovery, on its own
The Identify stage by itself. We spend time inside the operation and come back with what is worth changing, what to leave alone, and what each would take. Nothing gets built until you decide something should be.
The four-week capability engagement is the one fixed-fee offer we run, and its fee is quoted in the first conversation. Everything else is scoped and priced in writing before work begins.
The engagement
Three stages, carried on one piece of work.
Identify, Define and Ship are how every engagement runs. To keep them from being abstractions, one piece of work is carried through all three: a request to fix something in a building.
A resident reports it by phone. It has no owner, no record of having been made, and whether it is done is settled by a call.
It has an owner and a state from the moment it arrives, agreed steps in order, and a resident who confirms the repair from a phone before the record closes.
Identify · What we discover
Find the work worth changing.
We sit with the people doing the work and follow real decisions, handoffs and the cases that do not fit the rules. Leadership says what matters most. The operation shows what actually happens. The gap between the two is where the work worth changing usually is.
You receiveA ranked view of what is worth changing, and what to leave alone.
Two sources, read against each other
- Fewer repairs that drag past a week
- Residents who know what is happening
- Vendors dispatched without chasing paperwork
- Requests live on a board beside the accounting system
- One coordinator knows who covers which building
- Whether a repair is done is settled by phone
- Repair requests, from report to confirmationEffortModerateWorth changingHigh
A request that arrives by phone has no owner and no record of having been made. Who covers which building lives in one coordinator’s head, and the resident hears it is finished only if someone remembers to call.
- Vendor invoice matchingEffortHighWorth changingModerate
- Move-in inspectionsEffortLowWorth changingModerate
- Recurring filter changesEffortLowWorth changingLeave alone
Define · What we design
Design how the work should run.
We design the new way of working with the people who own it: the order of the steps, what the system does, who is accountable, the points where a person has to decide, and what each piece is built from. It is agreed in writing before anything is built.
You receiveA written definition of how the work will run and what it is built from, agreed before anything is built.
Defined · one repair request, end to end
- EntersA request arrivesA resident reports it from a phone, with a photo and a sentence. It has an owner and a state from that moment.
- SystemThe facts it may seeThe unit, the building’s covering technician, the vendor’s insurance dates — and nothing beyond what the rules allow.
- SystemAgreed steps, in orderAssign by rule, schedule, do the work, mark resolved. A missing input stops the run and is asked for by name.
- PersonThe resident confirms, or reopensThe one move the office cannot make on anyone’s behalf.
- OutputA result, and how it was reachedClosed by the desk, with every step on the record.
What it is built from, agreed with the scope
- Used as it isThe operating platformThe console, the workflow engine, the grounded assistant and the governed data layer: the components we bring. They run in your environment and are not rewritten for one building.
- Configured or integratedThe platform, set up for this workAn operating center for property in the console. A work-order workflow with its readiness rules in the engine. The assistant answering from the request record. The accounting system integrated, so a request and its vendor invoice meet in one place.
- Built newThe resident’s phone surfaceReport, photo, confirm or reopen. Nothing we bring puts that one decision in the resident’s hand, so it is built for this operation and stays with it.
Where each piece falls is written into the scope. Starting from the platform is why a definition is not a blank page, and why new software is built only where nothing we already have does the job.
Ship · What we build and put into use
Build it. Put it to work. Improve it.
We build what the definition names, in the proportions the scope set, and test it with the people who will use it. Then we stay while your team takes it on: what it produces is reviewed with them, and the system changes when they decide it should.
You receiveA running capability in the operation, and a team that can change it.
The same repair on the coordinator’s record when it went out and again once it was costed, and on the assigned vendor’s list as it stood when the job reached them.
The requestas it reached the desk
WO-1047TriagedKitchen sink backing up — standing water under disposal
Resident reports the kitchen sink will not drain and water is pooling in the cabinet beneath the disposal. Cabinet base is wet; resident has stopped using the sink. Triaged as high — active water intrusion into casework.
Next moves
- Assigned
- Cancelled
Vendor
Not assigned
Costs
No costs entered yet
Activity
- 22 Sep · 08:14Resident called at 8:05. Sink will not drain, water pooling in the base cabinet. Advised her to stop running the disposal and to clear the cabinet.
- 23 Sep · 17:30Same riser as the 1A laundry drain we’re working. If the tech finds the branch line blocked rather than the trap, flag it before he starts cutting.
The assigned workon the vendor’s own list
Marcus ElleryOutside vendor · signs in by linkAssigned to you
- WO-1047AssignedKitchen sink backing up — standing water under disposalDue 25 Sep 2026
- WO-1037In progressLaundry room floor drain slowDue 24 Sep 2026
- WO-1039ScheduledWater heater thermostat replacementDue 25 Sep 2026
- WO-1043ResolvedToilet running continuouslyDue 22 Sep 2026
- WO-1034VerifiedKitchen faucet cartridge replacementDue 19 Sep 2026
- WO-1031ClosedHot water pressure low in showerDue 16 Sep 2026
The completed recordback at the desk
WO-1047ResolvedKitchen sink backing up — standing water under disposal
Resident reports the kitchen sink will not drain and water is pooling in the cabinet beneath the disposal. Cabinet base is wet; resident has stopped using the sink. Triaged as high — active water intrusion into casework.
Next moves
- Verified
- In progress
Vendor
Marcus Ellery
Costs
$227.50
- Labour
- Cleared branch line to riser, reset trap
- $185.00
- Materials
- P-trap kit and cabinet base gasket
- $42.50
Activity
- 22 Sep · 08:14Resident called at 8:05. Sink will not drain, water pooling in the base cabinet. Advised her to stop running the disposal and to clear the cabinet.
- 23 Sep · 17:30Same riser as the 1A laundry drain we’re working. If the tech finds the branch line blocked rather than the trap, flag it before he starts cutting.
- 24 Sep · 11:15Marcus cleared the branch line back to the riser and replaced the trap assembly. Resident confirmed the sink drains and the cabinet base is dry.
Running · and what happens next
- Recorded, from the day it runsBuilt for the desk and the technicians to work in. Everything done there is kept: corrections, reopened requests and the exceptions people raise.
- Reviewed with the ownersThe owners of the work read what it produced together, on a cadence your team sets.
- Updated when they decide, and tested before it goes backA rule, a threshold or a step changes — or the finding is that nothing should — and it is tested against what was agreed before it returns to use.
What stays yours, and who supports it.
Which is which is settled in the agreement before work starts, along with how the engagement ends.
Your data and operating knowledge
Your records, your numbers, your definitions and your decision history stay in your environment. Nothing confidential is pooled between clients.
The implementation built around your operation
The workflows, the configuration and the application work built around your operation are yours.
The components and tools we bring
They stay ours, licensed to you where your system uses them. What travels is method and technology: the shape of an approval, a close, a queue, and the components that run them.
Third-party software and models
Your existing systems and the model providers keep their own terms.
An engagement can end with your team running it, or with us alongside as the work changes. Where each system stands is stated, system by system, in the case studies.
Tell us what you want to change.
Bring us an operating problem, a new opportunity, or an AI mandate that needs turning into work people can do.