aki · indie software studio
N 52.5200° · E 13.4050°
v0.1

we build quiet
software
for small teams.

01 / approach

three modes of working together.

Most engagements settle into one of these shapes. We name them up front so you know what we're committing to, and what we're not.

mode 01

The pilot.
Six weeks.

A fixed-scope sprint to test one risky assumption with a working artifact. Comes out with a small piece of real software and a written read-out of what we learned.

6 wks · 1–2 of us
mode 02 · most common

The build.
Three to nine months.

A full engagement to design, prototype and ship a product surface end-to-end. You get a small senior team operating like a lab inside your company.

3–9 mo · 2–3 of us
mode 03

The residency.
A year, or two.

For unusual problems that need long sit-time. We embed, write, and ship gradually — often co-authoring research alongside the build. Limited to one per year.

12–24 mo · 2 of us
02 / ethos

small teams, long sittings, plain software.

A short list of things we believe enough to organise the studio around.

how we work

We stay small on purpose.

Every project has one accountable lead from kickoff through shipping. The deck stays the same as the team. Less hand-off, fewer agendas, more time spent inside the actual problem.

  • 01One lead, accountable to you, from week one to week last.
  • 02Two engagements at a time, never more.
  • 03Written read-outs every two weeks; no status meetings.
  • 04Fixed fee, scoped per phase. No surprise change orders.
what we ship

Plain, durable software.

We're suspicious of novelty for its own sake. The interfaces we like are the ones that fade into the workflow — keyboard-friendly, fast on a five-year-old laptop, and legible to whoever inherits the codebase in 2031.

  • ·Native where it matters; web where it doesn't.
  • ·Boring tech stacks. Postgres, plain JS, plain Swift.
  • ·Documentation written for the next maintainer, not the launch tweet.
  • ·An exit ramp on day one: source, ops, and a handover doc.

have a problem
worth a chat?

typical replywithin 3 working days
wherebs as · remote-friendly