The Salesforce team that stays.
Development, administration and quality assurance under one accountable team. We have held a regulated government platform in production since 2021, through five years of releases.
The problems we get called on.
Most of our Salesforce work starts with an org someone else built. The first job is to understand it honestly, including the parts that are working.
- 01
The org has outgrown its build
Years of incremental change leave overlapping automation, unclear ownership and a release that nobody wants to sign off. We audit what is there, then stabilise it before adding to it.
- 02
Configuration has hit its ceiling
Clicks took the process a long way and then stopped. The next step needs Apex, Lightning Web Components, a proper data model and an integration contract that holds.
- 03
Quoting rules are the bottleneck
Product catalogues, price rules and approvals drift away from how the business actually sells. CPQ work is as much modelling the commercial rules as configuring the tool.
- 04
External users need their own slice
Customers, contractors and regulators all need part of the same record set and none can see the rest. That is a sharing and portal design problem before it is a build.
- 05
Support and delivery compete
One team cannot answer cases and ship a programme without a structure that separates them. We run both streams deliberately, with a hotfix path that does not derail the release train.
What the engagement
actually covers.
One team across the full platform surface. You do not brief a developer, an admin and a tester separately.
Development
Platform engineering where configuration runs out. Built to a trigger framework and reviewed, not written once and left.
Administration
Day-to-day ownership of the org: users, permissions, sharing, sandboxes and the seasonal release cycle.
Quality assurance
Testers inside the delivery team. Functional passes, portal regression and structured UAT verification before anything reaches production.
CPQ and commercial process
Quoting modelled to the way the business prices and approves. Product catalogue, rules and approvals treated as one design.
Integrations
Salesforce inside the wider estate. ERP, logistics, mapping and registry services, with error handling and retry designed in.
Communities and portals
Experience Cloud sites for customers, partners and regulated third parties, with visibility that follows the organisation hierarchy.
Einstein and Agentforce
Platform intelligence applied where it removes real effort, with the same testing and rollback discipline as any other release.
Mobile and offline field work
Where the work happens away from a desk. Native and cross-platform apps syncing against the org, built for no connection at all.
Data and migration
Getting records in, keeping them clean and moving them between systems without losing the audit trail.
Built for environments that get audited.
Our longest running Salesforce client is an Australian state government agency whose records have to be defensible to auditors and to the public. The method comes from that.
- 01
Audit before estimate
We read the org and the code before we price the work. You get an architecture position and an effort model you can challenge, not a number with nothing behind it.
- 02
Two streams, one team
A support stream takes cases, defects and small changes. A project stream delivers the larger capability. Both are staffed by named people who know the platform.
- 03
A release train with an exit
Versioned, scheduled releases through development, SIT and UAT sandboxes into production, with a separate hotfix path for work that cannot wait.
- 04
Security as a standing workstream
Access and least-privilege review, multi-factor enforcement and vendor advisory monitoring run continuously, not as an annual project.
- 05
Ahead of every seasonal upgrade
We assess each Salesforce release against your org before the upgrade window and report the impact while there is still time to act on it.
What you get,
and what you keep.
Every engagement is written so that leaving us would be inconvenient rather than impossible.
What lands in your org
Working software, documented and handed over properly.
- Code reviewed against a shared standard and deployed through pipeline CI
- Solution designs written per epic, so the reasoning outlives staff changes
- Test evidence: functional passes, regression runs and UAT verification
- Environment and release ownership, including sandbox refresh planning
What you keep
No dependency traps. The platform stays yours.
- Source control and pipelines in your accounts, not ours
- Configuration and deployment documentation maintained as part of delivery
- A named technical lead who can brief your auditors directly
- A backlog and roadmap you can hand to another supplier if you ever choose to
What we work in.
The platform surface we hold day to day, alongside the delivery tooling around it.
Salesforce in production.
Long-running platforms, external portals and field applications syncing against the org.
Five years of Salesforce platform delivery for an Australian state government agency
Continuous build, support and release management of the Salesforce platform an Australian state government agency uses to run a statewide regulatory compliance programme.
Read the studyOffline-first field inspection app for an Australian state government agency
Offline-first field inspection app for an Australian state government agency, in production under our support and being rebuilt around a new sync engine and design system.
Read the studyDocument intelligence for an Australian state government agency, turning survey PDFs into audit-ready Salesforce records
An AI platform that reads consultant inspection reports and writes structured, source-traceable register records into the agency's Salesforce org.
Read the studySend us the org,
not just the requirement.
We will look at what is there and tell you what we would change first. That conversation costs nothing.