Three disciplines we go deep on, and nothing else.

Salesforce architecture & engineering

Data model, sharing model, and platform boundaries designed before the build — then built by the people who designed them.

The work

• Data model and object design, including the sharing and visibility model
• Apex, Lightning Web Components, and Flow — chosen per problem, not per fashion
• Technical audit of an existing org: automation inventory, limits exposure, technical debt, and a prioritised remediation backlog
• Release process, environment strategy, and deployment tooling
• Code review and technical leadership alongside an in-house or partner team

We are two senior engineers, not a staffing firm. We take work where the architecture and the build matter more than the headcount, and we say so when a programme needs a larger delivery team than we are.

Enterprise integrations

Interfaces between Salesforce and the systems that own the data — designed for the day they fail, not just the day they ship.

The work

• System-of-record mapping: which system owns each entity and field, and in which direction it may change
• Interface design across Salesforce, ERP, finance, and operational systems — including MuleSoft-based delivery where it fits the landscape
• Idempotency, retry, and replay behaviour, with a dead-letter path for messages that cannot be processed
• Reconciliation jobs that detect divergence between systems rather than assuming it away
• Operational instrumentation: what is logged, what is alerted on, and what a first responder can actually do about it

We design and implement integrations for a specific customer landscape after discovery. We do not sell prebuilt connectors, and the systems listed in our integration catalogue describe delivery capability and past experience — not shrink-wrapped products.

Document intelligence

Turning documents into structured records you can audit — extraction with confidence scores, source evidence, and a review path for anything uncertain.

The work

• Document workflow design: intake, classification, extraction, review, and the record that results
• Confidence thresholds and human-review routing calibrated on the customer’s own documents
• Structured e-invoice handling, where the data is read from XML rather than inferred from a picture of a page
• Integration of extraction output into Salesforce or back-office systems as real records, with an audit trail
• Evaluation on a customer sample set, so the accuracy discussion is about your paperwork rather than a vendor benchmark

We do not publish a headline accuracy figure, because we have no benchmark methodology on record that would make one meaningful. We would rather run your documents and show you the result.