One product live, two in the worksLast shipped 4 Sept 2026Founded 2026

One platform.
Many products.
A release every week.

Tangudu Systems builds and operates its own SaaS products — no client work, no bespoke builds, no feature written for one logo. The same small team writes it, sells it, deploys it, and picks up the phone when it breaks.

ProductsEvery product is built, sold and operated by us.

Live

SchemeBook

Savings-plan software for multi-store retail. Enrolment, scheduled collections, maturity payouts and automated customer receipts — one console for the shop floor and the back office.

CategoryVertical SaaS
PricingPer store, monthly

Visit schemebook.app

Pre-launch

Vybro

Direct booking for backpacker experiences in Southeast Asia. Travellers pay in their home currency; hosts pay no commission.

CategoryMarketplace
Launching onThe Ha Giang Loop

In discovery

Usher

A floating button on any app or site. People say where they want to go — “my invoices”, “add a user” — and Usher takes them there.

CategoryDeveloper platform
Ships asOne script tag
How we build

A week is our longest unit of planning.

Most software companies are slow because of the distance between the person who decides and the person who ships. We removed the distance — same people, both jobs.

Ship weekly, not quarterly

Every product goes out on a weekly train. Anything that can't be finished in a week gets cut down until it can, or shipped behind a flag. Roadmaps are a direction, not a calendar.

Own the whole stack

We write it, we deploy it, we're on call for it. Nothing is thrown over a wall, which is why a bug found on Monday is usually gone by Tuesday.

Talk to customers, not about them

No account managers standing between us and the people using the software. Whoever writes the feature is whoever heard the complaint.

The platform

Product two took four months, not four years.

Every product sits on the same foundation — identity, billing, permissions, audit, notifications, design system. That's the whole argument for building several products under one company instead of several companies: the second one starts at the eightieth percentile.

Identity & accessOne sign-in, one permission model, one audit trail across every product.
BillingSubscriptions, invoicing and dunning built once and reused.
Data & eventsShared event bus and warehouse, so reporting isn't rebuilt per product.
Design systemOne component library. New screens ship in hours, not sprints.
Changelog

What went out recently.

Published every Friday, whether it was a big week or not. The gaps are as informative as the entries.

ReleasesNewest first.
SchemeBook

Customer passbook. Customers sign in with a phone number and an OTP to see every installment they've paid, and download a PDF statement.

SchemeBook

Books that can't be quietly edited — gapless receipts, versioned scheme rules, and every financial action logged with actor and timestamp.

SchemeBook

WhatsApp reminders ahead of each due date, with a pay link attached. Falls back to SMS when the message doesn't land.

Careers

Small team. Your work in front of customers in week one.

No tickets handed down, no six-week onboarding. You pick up a problem, you talk to the shops that have it, you ship the fix.

Open rolesSeven open across field, engineering, support, design and growth.

Tell us what's slow, and we'll tell you if we're building it.

We pick our next product from conversations with people running the software we'd have to replace. If that's you, we'd like an hour.

hello@tangudu.com