Guides
Technical notes, written for the build.
For admins, architects and delivery leads: eight notes on implementation, integration, agents and ops. When a guide is not enough, send the problem and hear back within 24 hours.
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.
Where each guide sits
One project, in the order it hurts.
Before the build
Process, objects, and what to refuse before anyone writes Apex.
Before cutover
Source, mapping, and the week the old system is allowed to die.
During the build
Pick the pattern from the failure mode, and name which system owns each record.
Before the audit
Who can see a record, why, and who approved it.
After go-live
Queries, limits, and the org that got slow.
Running a program
MuleSoft delivery and agent program ops
Named owners, receipts, and an escalation map.
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.
Who these are for
The admin, the architect and the delivery lead.
Example
Salesforce admin, Dubai property management company
Today: Inherited an org where three people stacked automation on the same object, and pages now crawl.
After: The performance guide shows which of the three usual causes they have before anyone rewrites code.
Property managementExample
Integration architect, Riyadh distributor
Today: The ERP and Salesforce disagree on who the customer is, and finance has noticed.
After: The integration patterns guide starts with naming the owner of each record, then picks the pipe.
MuleSoftExample
Delivery lead, US software company
Today: A migration from an old CRM is scheduled and nobody has rehearsed a rollback.
After: The migration guide puts the sandbox check and the rehearsed rollback before cutover.
For CTOs
The brief
Send the problem the guide missed.
One email starts it. We ask about the guide and the org after. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

