Guides
Technical notes, written for the build.
The first week is in the org, reading what already exists. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Guides
Eight guides. Pick your problem.
Implementation, integration, agents, and ops. If you are choosing a partner rather than solving a build problem, start with Resources instead.
Implementation
Planning, objects, and what to refuse before you write Apex.
Data migration
Source, mapping, and the week the old system is allowed to die.
Integration patterns
Reuse when it is real. A pipe when it is not.
MuleSoft delivery
Foundation, scale, then data. Named owners. Receipts, not slides.
Agent program ops
A claim, a receipt, and an owner. Escalation is a map.
Spec-driven engineering
Specifications, guardrails, shadow mode, and fleet operations.
Security and compliance
Sharing, identities, and what an auditor would ask.
Performance
Queries, limits, and the org that got slow.
How we work
When the guide is not enough.
- 01Week 1 in the orgWe read what already exists before anyone adds a cloud.
- 02Written noteWhat is worth fixing, what is worth finishing, and what is not. Not a dashboard.
- 03Fixed scope and priceWe can fix-price a named, scoped piece once the process is clear. We will not fix-price a rescue we have not assessed.
- 04BuildWe implement around the process you already run.
- 05We stayAfter go-live, a person stays on the exceptions.
The brief
Send the problem the guide missed.
One email starts it. We ask about the guide and the org after.