Where most teams are
When your customers run Salesforce, your product has to connect to their org, with their custom fields, their API limits and their security team's requirements. Our engineers build that connection into your product: OAuth, Bulk API syncs and field mapping that copes with every org being set up differently.
What our Salesforce developers do
External Client Apps and OAuth
Customers connect their org with OAuth through an External Client App, the successor to connected apps, so no passwords are shared. We ask only for the scopes you need.
Inside the daily API limits
Every org has a daily cap on API calls, shared with its other tools. We listen for change events instead of polling and use composite or bulk requests wherever they save calls.
Bulk API 2.0 for big data
Moving thousands of records one call at a time burns limits and times out. We run Bulk API 2.0 jobs for large imports and exports, and check each job's failed rows.
Custom objects and fields
No two orgs look alike. We read each org's metadata, map custom objects and fields per customer and test in a sandbox before anything touches their live data.
How it works
- 01
Pick how to work
One Salesforce integration, priced upfront and starting at $1,000, or a retainer from $4,000 a month for ongoing work.
- 02
Map the orgs
A senior engineer maps the Salesforce objects and fields you need, your API budget and how your customers will connect.
- 03
Ship and roll out
We build, test in a sandbox and roll out one org at a time. The engineer doing the work is on your calls.
Starting at $1,000
One integration, one fixed price, agreed after a short call. Single integrations start at $1,000. Need ongoing work? Part-time retainers from $4,000/month, month to month. Connecting more than Salesforce? See API integrations.
Talk to a Salesforce developer
rebuilt our onboarding, shipped our Zapier integrations, and wrote integrated plugins for our proprietary tools - all in record time. He ships better than we spec. This team is literally an extension of mine.
Work we've shipped
AI · Analytics
Better Analyst (formerly FormulaBot)
An analytics app used by 1.5M+ people. We built its 40+ data connectors, BigQuery to Postgres.
Consumer · FinTech
Finance Girlie
A personal finance platform for Muslim women. We built Plaid bank linking and transaction sync.
B2B SaaS · Client portals
KeepTrack
A white-label client portal. We built its Calendly scheduling and Stripe milestone payments, no platform cut.
How we can help
Four ways to work with us - pick what fits, switch when it doesn’t.
Audits
Find what's broken - or whether AI is worth it - before you build.
Learn moreMVP Sprint
Zero to production in 5-6 weeks. A real product, not a prototype.
Learn moreRetainer
A senior engineer embedded on your team, month to month.
Learn moreCode Rescue
Vibe-coded app breaking under real users? We rebuild it to hold.
Learn moreFAQ
Frequently asked questions
How much does a Salesforce integration cost?
A single integration has one fixed price, agreed after a short call. Prices start at $1,000. Ongoing work runs on a retainer from $4,000 a month, month to month.
How do you stay within Salesforce API limits?
By counting calls, syncing only records that changed, and using composite and Bulk API requests that do more per call. Your app shares each org's daily limit with other tools, so we leave headroom.
Can each customer map their own fields?
Yes. We build a mapping step so each customer can match your fields to their standard and custom Salesforce fields, with sensible defaults.
Can you connect our own Salesforce org, not our customers'?
Yes, and it's simpler: one org, one sandbox to test in, and the same care with API limits and field ownership.
We already have a connected app. Is that a problem?
No. Existing connected apps keep working. New connections are built as External Client Apps now, so we build yours that way and move the old one over when it makes sense.
Do you test against real Salesforce orgs?
Yes, in the right order. We build and test against Salesforce sandboxes and developer orgs first, then roll out to a customer's production org once the sync is proven.
Do we own everything you build?
Yes, 100%. You own the code, infrastructure, docs and credentials.
