Salesforce integration and development
We do the integration and front-end work around Salesforce. We do not sell licences.
We build the systems that talk to Salesforce: website and portal integration, two-way data sync that survives an API limit, Lightning Web Components, and customer-facing interfaces that read and write records without putting the CRM on the public internet.
Where we fit around Salesforce
Salesforce is the enterprise CRM: endlessly customisable, wired into how large sales organisations actually run, and expensive enough that most of its value depends on what is connected to it. Let us be clear about our lane. We are not a Salesforce implementation consultancy. We do not sell licences, run org-wide transformation programmes or configure Sales Cloud from a blank org. We build the software around it.
There is a great deal of real work in that. Websites that create leads without losing them when the CRM is having a slow morning. Customer and partner portals that read and write records through a middleware layer, so Salesforce is never directly exposed. Two-way synchronisation with an ecommerce platform, an ERP or a support desk, designed so a retried job or a replayed webhook cannot duplicate a record. Lightning Web Components where an internal screen needs behaviour the standard interface will not give.
The failure mode is always the same, and it is always avoidable. Naive integrations assume the API is available, fast and idempotent. Salesforce has governor limits, API quotas and maintenance windows, all of which are documented and none of which are optional. We design for them: queues instead of synchronous calls, bulk operations instead of record-by-record, a named record of truth for every field, and reconciliation that surfaces drift rather than trusting it away.
If you need a full implementation partner, we will say so and step aside. If you need the website, the portal and the integrations around Salesforce to stop losing data, that is exactly our lane, and it usually starts with a look at the automation layer.
What we build around Salesforce
Website and form integration
Lead capture that queues and retries, deduplicates against existing contacts, and never silently swallows a submission on a bad afternoon.
Customer and partner portals
Authenticated interfaces in Next.js over a middleware layer, so customers see their own records without ever reaching the CRM.
Explore →Two-way data sync
Bulk-aware synchronisation with ecommerce, ERP and support systems, built around the API limits rather than into them.
Lightning Web Components
Custom components and Apex services for the internal screens where the standard interface fights the process instead of supporting it.
Reporting pipelines
Salesforce data extracted into a warehouse or dashboard so marketing, finance and operations finally argue from the same numbers.
Explore →Middleware and API layers
One service between Salesforce and everything else, handling authentication, retries, rate limits and audit logging in a single place.
Explore →How we work with Salesforce
Salesforce compared with the alternatives
Salesforce vs HubSpot
Salesforce customises further and absorbs genuinely complex enterprise process, at considerably more in licences and specialist administration. HubSpot is faster to adopt and enough for most mid-market companies. If you already run Salesforce, our job is to connect it well rather than to relitigate a decision your board made three years ago.
Direct API calls vs a middleware layer
Calling Salesforce straight from a website works right up until an API limit, a maintenance window or a slow response costs you a lead. A small middleware service with a queue, retries and idempotency keys takes a few days to build and removes an entire category of incident permanently.
An Experience Cloud portal vs a custom front-end
Experience Cloud is quicker when the portal is simple and your users are already licensed. A custom Next.js portal over middleware wins when the interface has to match your brand, perform well in public, or serve people you have no intention of buying licences for.
Salesforce, answered
Are you a Salesforce implementation partner?
No, and we will not pretend otherwise to win a project. We build the websites, portals, middleware and integrations around Salesforce. For org design, licensing strategy or a full Sales Cloud implementation you want a specialist partner, and we work alongside several of them without friction.
How do you stop leads being lost between our website and Salesforce?
Never call the API from the request. The form writes to your own database and returns straight away, a queued job pushes to Salesforce with retries and an idempotency key, and a reconciliation job flags anything that failed to land. Nothing depends on Salesforce being awake at the moment a visitor hits submit.
Can customers see their Salesforce data on our website?
Yes, through a middleware layer with its own authentication and caching. The CRM never faces the public internet, your users do not need Salesforce licences, and you decide field by field what can be read and what can be written.
Can you sync Salesforce with our ecommerce platform or ERP?
Yes. The design work is agreeing the record of truth for each field and deciding how conflicts resolve. Then bulk operations to stay inside API limits, idempotency so replays are harmless, and a reconciliation report so drift is visible this week rather than next quarter.
Do you write Apex?
Where it is needed, for services behind Lightning Web Components or logic that has to live on the platform. We keep heavy business logic in middleware we can test and deploy independently, because Apex accumulates and every change then waits on a Salesforce release window.
How is Salesforce work staffed and priced?
Per engagement rather than at a published hourly rate, since integration scope varies enormously. Tell us the systems involved and which way the data flows, and you get a team and a rate in writing within two working days.
Salesforce connected to everything except what you need?
Describe the systems and which direction the data should flow. You get an integration design and an estimate back in writing.