Anchor Stack

Anchor Stack Web & mobile software studio 0 m

Software
that holds

We build websites and apps for ordinary problems — fares, savings groups, stock books, clinic queues. Things people use on a Tuesday morning, on a cheap phone, with two bars of signal.

What we build

Three things, cast heavy

Most software for everyday users is built as if everyone has a flagship phone and fibre at home. We start from the opposite assumption and it changes every decision underneath.

Web

Sites that load anywhere

Server-rendered, budgeted in kilobytes, readable before the fonts land. We test on a throttled 3G profile and a four-year-old Android before we call anything done.

  • Next.js
  • TypeScript
  • Design systems
  • Core Web Vitals

Mobile

Apps that work offline

Local-first storage, queued writes, conflict rules decided up front. The app keeps working in a basement or a bus, then reconciles the moment signal returns.

  • React Native
  • Flutter
  • SQLite sync
  • Push

Rails

Plumbing that connects

Payments, SMS and USSD, maps, identity, receipts. The unglamorous integrations that decide whether a product is usable by someone without a smartphone at all.

  • Payments
  • SMS / USSD
  • Auth
  • Webhooks

The stack

Five layers. Each one holds the one above it.

The name is not decoration. Pick any layer to lift it out of the assembly and see what it carries.

Selected work

Built for a Tuesday morning

None of these are dashboards for analysts. They are tools for a shopkeeper, a treasurer, a commuter, a clinic receptionist.

Chama

Savings groups

A ledger for rotating savings groups. Contributions reconcile against mobile-money statements automatically, and every member gets an SMS receipt — including the ones without smartphones.

4Taps to log
SMSFallback channel
0Spreadsheets left

Njia

Transit

Routes and honest fares for informal transit, crowd-sourced by the people who ride it daily. Maps and fare tables are cached on install, so the app is useful with the radio switched off.

1.4 MBInstall size
100%Offline routing
Android 7Floor supported

Duka

Retail

A stock book for a one-room shop. Scan or type, sell, restock. It never blocks on the network — the day's takings are on the device and sync when there is signal to spare.

LocalFirst write
~9 sDaily close
2Languages

Foleni

Health

A clinic queue that runs over plain SMS. Patients hold their place from home instead of on a bench at 6 a.m., and reception sees the same list on a browser tab.

USSDNo app needed
AnyHandset
LiveReception view

How we work

Sound it, then set it

Four stages, in order. Each one has to hold before the next is worth starting — which is the whole reason we named the studio this.

  1. 01 · 0 m

    Sounding

    Two weeks with the people who will use it, where they will use it. We measure the real problem — the queue, the notebook, the WhatsApp group doing the job today — before proposing anything.

  2. 02 · 120 m

    Setting

    We pick the smallest thing that holds: scope, architecture, the one metric that says it worked. You get a fixed price and a plan you can hand to someone else.

  3. 03 · 520 m

    Building

    Two-week cycles, each ending in something installed on a real device in real hands. No demo environments that only work on our laptops.

  4. 04 · 900 m

    Holding

    Launch is the middle, not the end. We monitor, patch, and keep shipping — or we hand over documented code and train your team to take the watch.

Two-week cyclesSomething shippable at the end of each one.
Fixed-price discoveryYou know the cost of finding out before you commit.
You own the codeYour repositories, your accounts, from day one.
We keep the watchMaintenance on what we ship, for as long as you want it.

900 m · Bedrock

Drop
anchor

Tell us the problem, not the feature list. If it is something an ordinary person runs into on an ordinary day, it is ours. First reply within two working days.

hello@anchorstack.dev