Hire Scala developers who've already shipped what you're building
Three ways to work with us. All three come with the same guarantee: senior engineers, direct communication, and a two-week checkpoint where you can walk away.
Scala staff augmentation
For: Teams with Scala systems and not enough Scala engineers.
Your embedded engineer joins your Slack, your repos, and your ceremonies. They're not a “resource” you route tickets to through an account manager — they're a teammate who happens to be invoiced monthly.
What's different from a body shop:
No bait-and-switch.
The engineer you interview is the engineer you get, for the life of the engagement. This is the most common failure mode of offshore agencies and we're happy to put it in the contract.
Senior only.
We don't staff juniors and bill them as mids.
Timezone coverage, not timezone excuses.
NZ hours mean live overlap with US Pacific afternoons and EU mornings.
Typical engagements: 3–12 months, monthly rolling after an initial commitment.
When staff augmentation is the wrong call
If you need fewer than ~60 hours of work, buy consulting instead. If the work is greenfield and self-contained, fixed-scope development will cost you less. We'll tell you this on the first call, but it's cheaper for you to know before it.
Custom Scala development
For: A defined system that needs building — and a team that needs to own it afterwards.
We design, build, and hand over. The handover is the point: you get documentation, architecture decision records, and a walkthrough with your engineers, not a zip file and an invoice.
Where we're strongest:
Event-driven backends
Kafka + Pekko/ZIO stream processing, exactly-once semantics where "pretty much once" isn't good enough
Financial systems
Ledgers, reconciliation engines, payment integrations, where correctness is a feature and the type system is doing real work
Data pipelines
Spark jobs that run faster and cost less, batch-to-streaming migrations
Pricing: Fixed scope where the spec is genuinely fixed; milestone-based where it isn't. We will not sign a fixed price on a vague spec and neither should you accept one from anyone — that's how projects end up in dispute instead of production.
Scala consulting & architecture review
For: Teams that need answers more than headcount.
Short, sharply-scoped engagements with a written deliverable:
Akka → Pekko migration assessment
Since Akka's licence change, most teams know they need to move and haven't priced the move. We audit your usage, flag the breaking points, and hand you a sequenced migration plan with effort estimates.
Effect-system architecture review
ZIO or Cats Effect codebase grown organically and now fighting you? We review, benchmark, and give you a prioritised refactor list — with the honest option of "leave it alone" where the cost exceeds the benefit.
Pipeline performance work
Spark and Kafka tuning with before/after numbers, not vibes.
Scala 2 → 3 migration planning
Including the recommendation not to migrate yet, if that's what your dependency graph says.
Typical engagements: 1–4 weeks, fixed fee, written report + recorded walkthrough.
What every engagement includes
A 45-minute technical scoping call with an engineer, free, no obligation
Written scope before any invoice
Two-week checkpoint with a no-fault exit
Direct Slack/email access to the engineers doing the work
Code that passes your review standards, or we fix it on our time
Not sure which model fits?
Describe the problem in two sentences and we'll tell you — including if the answer is “none of them.”