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.

Where each guide sits

One project, in the order it hurts.

  1. Before the build

    Implementation

    Process, objects, and what to refuse before anyone writes Apex.

  2. Before cutover

    Data migration

    Source, mapping, and the week the old system is allowed to die.

  3. During the build

    Integration patterns

    Pick the pattern from the failure mode, and name which system owns each record.

  4. Before the audit

    Security and compliance

    Who can see a record, why, and who approved it.

  5. After go-live

    Performance

    Queries, limits, and the org that got slow.

  6. Running a program

    MuleSoft delivery and agent program ops

    Named owners, receipts, and an escalation map.

Spec-driven engineering sits across every stage and has its own guide.

How we work

When the guide is not enough.

  1. 01Week 1 in the orgWe read what already exists before anyone adds a cloud.
  2. 02Written noteWhat is worth fixing, what is worth finishing, and what is not. Not a dashboard.
  3. 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.
  4. 04BuildWe implement around the process you already run.
  5. 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 management
  • Example

    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.

    MuleSoft
  • Example

    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
Examples of the readers these guides are written for. Not client stories.

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.