Work / Energy
Field data, compliance reporting and customer operations run through systems that were never connected. We build the operating layer that joins them — and the agents that keep them current.
- 0 agentsscoped for one solar installer
- 0 portalfor crews, customers and the office
- Weeklyscheduling that runs itself
Right now, every job runs through five systems and one coordinator.
Crews, materials, permits, customers and invoices are tracked in tools that don't talk — and the office spends its week reconciling them.
Scheduling by phone and spreadsheet
Material requests by text
Invoices raised days after completion A crew waiting on a permit
An invoice raised a week late
A customer nobody confirmed The manual only one person has readSame week. Same team. A different set of problems.
The decisions behind scheduling, materials, customers and invoices.
- Scheduling by phoneCrews, permits and weather juggled in a spreadsheet and a head.
- Materials by textWrong parts, second trips, nobody checked the job.
- Customers unconfirmedDay-before checks happen when someone remembers.
- Invoices days lateCash tied up and disputes later.
- Scheduling by phoneScheduling by engine
- Materials by textMaterials from a form
- Customers unconfirmedCustomers and crews reached
- Invoices days lateInvoices on completion
An agent deployment portal with a memory and knowledge layer, connected to Roofr, Slack, Gmail and the task tracker.
Platform
- Agent deployment portalWhere the office turns agents on and watches them run
- Memory & knowledge layerJobs, customers, crews and materials in one record
- Roofr API & MCP serverJob data in and out of the tool the crews already use
Integrations
- Slack & GmailRequests and updates where the team already talks
- Task trackingEvery agent action becomes a trackable task
- InvoicingRaised on completion, chased automatically
Agents scoped with the team
Eight agents, prioritised by what saves the coordinator the most hours.
- Scheduling engine
- Material requests
- Invoice & payments
- Customer & crew outreach
- Q&A knowledge agent
What the studio has shipped as a product, not a project. Each opens in its own site.
- Constraint
- Scheduling by phone, material requests by text, invoices days late — and one coordinator holding it together.
- System
- An agent deployment portal with a knowledge layer, a Roofr API and MCP server, Slack, Gmail and task-tracking integrations, with scheduling and material-request agents first.
- Result
- The weekly schedule runs from the portal; material requests arrive as orders; blockers are listed, not discovered.
“The schedule used to live in my head and a spreadsheet. Now it lives in the portal and I review it over coffee. (Simulated quote — see PLACEHOLDERS.md.)”
Tell us about one workflow. We'll come back within a working day with what a system would look like — then you pick a time.
- Map the workflow to the agents and systems that would run it
- Build inside the tools you already use — no new platform
- Move from a first increment to a system your team runs — in fortnights