We're a small studio. By the standards of the global SaaS industry we're a rounding error — 30-something people, one office in DMCC, four timezones of contract collaborators. And yet, in every quarter since 2022, we've won engagements where our shortlist included companies with 100× our headcount and a NYSE ticker.
The reasons clients give us in kickoff meetings are remarkably consistent. They're worth writing down — partly so we keep doing the things that earned the work, partly because if you're picking between a studio and a platform vendor for a hard problem, this is the comparison nobody publishes.
1. The team you meet is the team that builds it
In a global SaaS engagement, the people in the sales pitch are not the people who write your code. The people who write your code rotate. Your account manager rotates faster. The institutional memory of why something was built a particular way disappears in 12–18 months.
In a studio, the engineer who wrote your auth system is sitting in the same room as the engineer who's now extending it, and the principal who chose that architecture is two desks away. When you call about a weird bug 18 months later, somebody actually remembers.
This isn't a "studios care more" argument. It's a structural one. Continuity is a function of team size and turnover. Studios win on both.
Continuity is a function of team size and turnover. Studios win on both. — Jonas, in a kickoff with a GCC bank, 2025
2. Custom is custom, not a config flag
Big SaaS sells "configurability" the way airlines sell legroom. The promise is generous; the reality is a settings panel with 40 toggles, none of which solve your actual problem.
When a regulated GCC bank told us their compliance team needed an audit log structure that no off-the-shelf platform supports, the SaaS vendors quoted a multi-quarter feature request and a "we'll see if it gets prioritised." We shipped it in three weeks. Because we wrote the code, all of it.
Every category has its 80%-fit incumbent. The interesting work — and the work most worth paying for — lives in the 20% the incumbent can't ship.
3. We say no to 70% of inbound — and that's why we ship
Studios that say yes to everything become bad versions of agencies. We screen briefs hard, against a nine-question fit test that filters for: clear decision authority, real budget, technical ambition, and a problem we'd actually want to work on for a year. The 30% we take, we ship.
The economics are simple — 30 great clients pay better than 90 mediocre ones, and the work compounds because the case studies are all wins.
4. We pick the boring stack on purpose
We still ship Postgres + a well-chosen application framework + a small, sharp infrastructure footprint in 2026. Not because we're stuck in the past — because the boring stack pages on call less, hires more easily, and does not require a four-week onboarding for the next engineer to read the code.
Big platforms can't do this. They're trapped in their own product surface, even when a simpler architecture would serve the customer better. A studio can choose the right tool for your problem, not the tool that pads its annualised contract value.
5. The feedback loop is hours, not weeks
When a client asks "what if we tried X" in a Tuesday review, the answer on Friday is "we tried X — here's the prototype, here's what we found, here are the trade-offs."
That cadence is impossible at scale. Big SaaS has a quarterly roadmap and an OKR review cycle and a product council. The smallest decision goes through a process that's optimised for risk reduction at scale, not speed for one customer.
For 80% of work that doesn't matter. For the 20% that does — the strategic, hard, novel work — that cadence is worth more than every feature on the bigger product's spec sheet.
6. Outcomes, not seat licenses
The studio model and the platform model have fundamentally different incentives. A platform vendor wants you to use more of the platform. A studio wants you to ship the outcome.
Sometimes those align. Often they don't. When a SaaS vendor tries to talk you into a heavier integration or a wider rollout, ask whether it's the right answer for your problem or the right answer for their renewal. With a fixed-scope studio engagement, that question doesn't even come up.
What a studio is bad at
This piece is from one side of the comparison, and being honest about the other side matters. Studios are bad at:
- Massive horizontal scale. If you need a CRM for 80,000 sales reps across 14 countries, buy Salesforce. We are not the right call.
- Pure off-the-shelf. If your problem is genuinely solved by a $30/seat product, just buy it.
- 24/7 global support across many products. A studio supports what it built. A platform supports a portfolio.
- Compliance certifications you need yesterday. SOC 2, ISO, HIPAA — most studios have these for the products they own (Vero is SOC 2 Type II certified, ISO 27001), but a fresh build won't be on day one.
Pick the right tool. Sometimes it's us. Often it isn't. The clients we work best with are the ones who already understand that.
The work the gorillas can't do
The pattern across our best engagements is the same. The client tried a platform first. It got them 70–80% of the way. The remaining 20–30% — the regulatory edge case, the unique workflow, the integration nobody supports — was the part that actually moved the business.
That last 20% is the studio market. It's not a category that'll show up in Gartner. It's just where the most interesting software gets built.
That's the work we want.
Graffitecs is a small, loud studio in Lahore, Pakistan. Est. 2017. We build software, occasionally ship products of our own (Vero, DocEngine), and write things down when we have something to say.
