Already have an app?
We build the systems behind it.
For software companies, agencies and consultants who own the customer relationship: the APIs, data, integrations, business rules and AI access that make the product work.
You keep your customers and your interface. We make the machinery work.
Your customers see your product and talk to your team. We build what runs underneath, out of sight. If one of these sounds familiar, this page is for you.
A roadmap blocked on integrations
Customers keep asking for the connection to their accounting, CRM or payment system, and every one of them lands at the bottom of the roadmap because the team is busy with the product itself.
Good at selling, not at building a backend
You know the market and you support the customers well. What you do not want is to hire and manage backend developers to keep the data, rules and jobs behind the product working.
A promised tool with nobody to build it
You told a customer they would get a portal, a calculator or a report that updates itself. The relationship is yours; the build needs someone who builds this for a living.
What we build behind a product
The parts your customers never see but always depend on. A build can be one of these or all of them.
APIs
Documented endpoints your app, your customers or your partners call, built to be versioned so changes can roll out without surprising the people who rely on them.
Data pipelines
Data pulled from the systems your customers already use, cleaned, checked and stored in one shape your product can rely on.
Calculations and business rules
Pricing, scoring, eligibility, forecasts and the other rules that make your product yours, written once and tested, so every screen draws on the same rule.
Integrations
Connections to accounting, CRM, payment, scheduling and field systems, so information moves once, automatically.
Scheduled jobs
Nightly syncs, monthly reports, reminders and clean-up work that run on a schedule, without anyone pressing a button.
Permissions and audit trails
Who can see and change what, per customer and per user, with a record of changes so you can trace "who did that?"
AI and agent access
AI assistants and agents call your service through a documented, permissioned interface, so the AI owns the conversation and your product owns the work. You decide which data and actions each one can reach.
How we work together
- A written scope first
- Before any work starts you get a plain-language scope and an estimate: what we build, what you build, and what done looks like.
- Your repo or ours
- We can work in your code repository under your review process, or build in ours and hand the code over.
- Your cloud or ours
- The systems can be set up in your cloud account from day one. If you prefer, the written scope can stage them in ours during the build and move them to yours.
- Handover documentation
- Each build is handed over with written documentation of how it works, how to deploy it and how to change it, so your team can take it from there.
No lock-in: we build so another team can maintain the work, and the written scope says how the code and documentation are handed over if you take it in house or move it to someone else.
Proof
Two things we built, each with some of the machinery this page describes: imports, rules, calculations and an output people rely on. More of the systems we have connected, each with its status, are on the integrations page.
A direct-mail lead tool from raw county data
- Problem
- One of the solutions we've provided is a direct-mail lead tool. The problem: campaigns were built from raw county parcel exports, well over 150,000 rows, and the list was cleaned, filtered and scored by hand before every mailing.
- Approach
- We built a browser-based tool that imports the county file, cleans and categorizes the columns, filters and scores parcels on things like acreage, absentee owners, and zoning, tracks each lead through a status lifecycle with suppression and a randomized holdout group, and exports a print-ready mailing list with one letter per household. The data stays in the browser and nothing is uploaded.
- Result
- A working path from a raw county file to a deduplicated, print-ready mailing list, with the printed output checked to match a separate build script exactly so the two never quietly disagree.
An analytics layer over accounting data
- Problem
- Small business owners have their numbers locked inside their accounting software but rarely have time to turn them into the analysis a CFO would run.
- Approach
- We built 2diff Business to connect to a business’s accounting software through its API and read the reports, never writing anything back to the books. It produces full financial statements, a set of ratios across profitability, liquidity, leverage, and efficiency, forecasts, a business valuation, and plain-language observations about what the numbers show.
- Result
- A live product with a free, login-free demo that runs on realistic sample data, so a business owner can see the analysis before connecting anything of their own.
What happens next
You describe the problem
A few sentences about what is not working and what you wish existed. No formal spec, no commitment.
You hear back from the founder
You hear back from Matthew Dettman, the founder, who scopes and builds the work. If it is not something we can help with, we say so plainly.
A free 1-hour session
We make sure we understand the problem and tell you honestly whether it is worth building and roughly what it would take.
A written scope and a fixed quote
Before any work starts, you get a plain-language scope and a fixed quote. You decide whether to proceed. No retainer unless you want one.
Tell us what your product needs.
Describe the product and the part that is stuck. We tell you honestly whether we are the right fit for it, and you get a written scope and a fixed quote before any work starts.
or email info@2diff.ioBook a free 1-hour AI Session (opens in a new tab)
Need software for your own business instead? See everything we build.