Your systems work fine until someone needs last month’s receipts

Your business probably runs on a spreadsheet, a group chat and one person who remembers everything. I build apps and automations on top of everything you already work with, streamlining your team into a unified entity.

BeforeAfter

The group-chat dig

Receipts, quotes and decisions sit weeks back in the group chat, and every Friday someone scrolls up to August with a coffee to find them.

One record, everywhere

The sheet you already have becomes the database. The app, the dashboard and the client page all read from it, so nobody types anything twice. Locked saves, rate limits and idempotent writes keep the same booking or task from landing twice.

The human hard drive

One person knows where everything is, which works well until they go on holiday.

Work that chases itself

Status, reminders, translations and follow-ups update on their own, so a manager can read the latest without asking for it.

The copy-paste olympics

The same client gets typed in twice, and commission is worked out on a phone calculator, booking after booking.

Numbers you can check

Rp1.043.000 found in a group chat and 62 tasks pulled out of a meeting log. Every figure in the case studies comes from the real build.

Tools your team will actually open

Task trackers that answer “who’s on it?” before anyone asks. Booking apps that fill the calendar while you’re still answering the last message. Quote pages that close the deal before the client closes the tab. Dashboards a director reads in one scroll. And automations for whatever your team is still copying and pasting by hand.

  • Task and project trackers

    Who owns what, by when, worked out from the dates. Numbered the way your team already talks, so nobody learns a new language to find task 2.14.1.

  • Apps for the team’s phones

    Runs on whatever holds your records today, from a spreadsheet to a paper logbook, so tasks, updates and site photos come in from anywhere. No app store download, no per-seat fee.

  • Multilingual tools

    Tasks and updates are translated automatically, so a Russian site lead and an Indonesian crew read the same record. Any language your team works in, and a translation never overwrites what a person typed.

  • Chat-to-task

    Paste the group chat in and get draft tasks with owners and deadlines. Duplicates are flagged before anything saves.

The builds, screen by screen

Forty-eight real screens from four apps. Open any one full size.

Axiom
Task manager in English and Russian
Google Sheets, Apps Script, Gemini
Mobile web app for a construction team in Bali
Sign inTeam code, then pick your name
TasksFilter by project, status and owner
UrgentFlag any task, grouped by project
Weekly planLast week’s results and this week’s plan
TaskStatus, week, urgency, carry-over with reason
ProtocolSame numbering as the meeting protocol
From chatGemini turns a pasted chat into draft tasks
New taskNext protocol number assigned automatically
Tap any screen to open itRead the case study

Five builds, opened up

What each team had, what I built on top of it, and what changed.

Axiom Task Manager

From a weekly meeting log to an app the site team uses.

Client
PT Axiom Construction Co, Bali
Role
Director; designed and delivered it
Team
English and Russian speakers
Timeline
October 2026, ongoing

The gap

Action items buried in a meeting log

Axiom is a team of experienced engineers doing interiors and renovations across four live projects: Villas Seseh, 8SENCE, Angel Cakes Uluwatu and Anantara Dragon. There was no task system. Actions lived inside the weekly protocol, one tab per project, in long status-log cells with no deadlines anyone could track.

The team works in English and Russian, and the protocol had to stay as it was because people still used it every week.

What I built

One record, linked to every stage

A task manager in Google Sheets with Apps Script, then a custom mobile web app on top. The protocol stays the meeting and finance record. The new system holds every action item, linked to its project stage.

Numbering the team already used, now automatic

2.14.1
2 is the section, for example finishing works14 is the stage; the next free number is suggested1 is the side: .1 contractor, .2 client

Uploads file themselves into Сесех / 2. Отделочные работы / 2.1 Фасады / 2.1.1 Подрядчик

What the app does

Status from datesOverdue to done
Automatic translationEnglish and Russian
Chat-to-task inboxDuplicates flagged
Site photosThe right Drive folder
Owner and participantsA “mine” view
New project or stageFrom the phone
  • 62tasks moved out of the protocol
  • 190dated updates kept as history
  • 4live projects, one system
  • EN⇄RUevery task, both languages

How it came together

  1. Task manager in Sheets

    Owners, priorities and status flags with EN⇄RU translation, then an inbox that turns pasted chats into draft tasks.

  2. Protocol migration

    Read the protocol without editing it, extracted every open action and its dated history, linked each to its stage and side.

  3. Protocol view

    A view that reads like the meeting log the team knows, built from the new task data.

  4. Mobile web app

    Built from the team’s feedback: auto-numbering, file uploads, participants, deadlines. Chosen over AppSheet to match the design and cost nothing per user.

«Наташа, привет еще раз! С Андраником обсуждали текущую версию приложения, в целом очень все нравится.»

“Natasha, hi again! Andranik and I talked through the current version of the app. Overall, we really like everything.”

Dmitry Semenov, Axiom
  • Google Sheets
  • Apps Script
  • Gemini API
  • Google Drive
  • Mobile web app

KRIYĀ Studio App

The whole studio runs on the sheet it already had.

Client
KRIYĀ tattoo studio, Bali
Role
Owner; designed and built it
Built on
The studio’s existing Main Sheet
Timeline
August to November 2026

The gap

A working sheet that made people retype everything

The studio already ran on a Google Sheet: a bookings log, a client CRM and an income dashboard. But a single booking meant twelve typed fields, clients entered twice, and prices and commission worked out by hand. Quotes lived in DMs, nobody could see who had done what that day, and nothing caught two clients booked into the same chair.

What I built

One link, three pages, the same sheet underneath

The team app, behind a studio code, gives everyone a daily checklist, a team view of who is done, tasks that can’t be marked blocked without saying what they wait on, a quote calculator for walk-ins and DMs, bookings with clash warnings, and open books where each person sees their own commission.

The request page is public. Clients describe their idea and see a rough price range before they even ask.

A private quote page goes to each client with a secret key in its link. They accept and pick a day, or make an offer. Offers below the low end of the quote go to the owner. The team gets an email either way.

BeforeIn the app
12 fields typed per bookingClient, time, hours, placement, style
Prices worked out in DMsQuote calculator and a private quote link
Haggling in the chatOffers logged; below the floor needs the owner
No view of the day’s workDaily checklists and a team view
“Stuck” with no reasonBlocked tasks say what they wait on
Commission by handOpen books, 20% worked out per rep

Try the quote rules

about 2.7 h of work
Pieces1
EstimateRp2.500.000 to 3.500.0002.5 to 3.5 h in the chair

9 cm of minimal line is one hour at Rp1.000.000, with a one-hour minimum. The app shows the same rules; the range here is simplified.

The client’s path

  1. Request
  2. Rough price
  3. Private quote
  4. Accept or offer
  5. Pick a day
  6. Deposit

Every step writes back to the same sheet, so the income dashboard and CRM keep working as they always did.

  • 3pages from one link
  • 16screens across team and client
  • Rp1jtan hour, 1-hour minimum, built in
  • 0new software for the team

Ludwig

A language app where the teacher’s lessons become the student’s homework.

Client
Private Indonesian tutoring
Role
Developer; designed and built it
Stack
Vite, Supabase, Netlify, GitHub
Timeline
November 2026

Try the review schedule

New card
makanto eat, есть
1-2 Learning3-4 Known5-6 Mastered

“Again” brings a word back in a minute. “Got it” and “Easy” move it up one or two boxes, and each box waits longer: 1, 3, 7, 16, then 35 days.

What students get

TodayDaily goal, word of the day
FlashcardsThree-button grading
Match Rush and Cat HuntTwo games
ReadingTap to translate and save
MemoryThe forgetting curve

The gap

Lessons and practice lived in different places

A student learning Indonesian from Russian had good lessons and generic apps, and nothing connecting the two. Words taught on Tuesday never showed up in Wednesday’s practice, and the teacher couldn’t see what had stuck.

What I built

One app, two sides of the same lesson

Students sign up, wait for approval, then practise word decks with spaced repetition and read short stories with questions. They switch between English and Russian explanations.

The teacher approves students, logs the words taught in each lesson, keeps private notes, and writes decks and stories in the app instead of code. A word logged after class appears in that student’s Dari guru (“from the teacher”) deck straight away.

Students get reasons to come back: a Today screen with a daily goal and a word of the day, two games (Match Rush, six pairs against the clock, and Cat Hunt, a pixel game starring three real cats), stories where any word can be tapped to translate and save, and a Memory view that turns Ebbinghaus’s forgetting curve into a personal recall estimate.

It started as a lean practice app for one learner and grew into a platform for several students in the same week, without changing hosts or adding a server.

The security rules live in the database

Every table has row-level rules, so even someone poking at the app’s code only gets what their role allows. Pick a role:

  • 10/10tables with row-level security
  • 112words in 8 starter decks
  • EN, RUexplanations, Indonesian practice
  • 0servers to maintain

PawinBali

A WhatsApp group for every booking, replaced by one private page per client.

Client
PawinBali pet care, Bali and Surabaya
Role
Developer; designed and built it
Stack
Supabase, Apps Script, Drive, Netlify
Timeline
November 2026

The gap

Bookings that lived in DMs and group chats

Clients booked through Instagram DMs. Totals were worked out by hand, dates were typed into a calendar, and every booking got a WhatsApp group of its own, where the photos, the payment and the questions all piled up.

What I built

One link per client, one view per role

Clients get the booking link from an automatic reply to their DM. They choose Bali or Surabaya, one of four services, the nights and a sitter, and watch the total add up. Full days are struck out and busy sitters greyed. They pay by bank transfer to that city’s own account, attach the screenshot, and get a private pet page that stays the same for every stay: the latest photo, every earlier one, a ring counting down to the next, and stars for the sitter after pick-up.

Admins log in with a phone number and a six-digit code. One Today page covers both cities: stays in progress, updates due, updates late and payments to check. A photo ten minutes overdue turns the row orange, and one tap reminds the sitter. Every transfer sits beside the amount expected before anyone presses Confirm and book, which puts the stay on that city’s Google Calendar.

Sitters see only their own day. They can’t post an update without a photo, and their reviews travel with them.

PartWhoHow they get inWhat they do there
Booking pageClientsThe link from an Instagram DMChoose city, service, days and sitter, and see the total
Pet pageClientsTheir own private link, the same every stayPay, follow photo updates, see past stays, leave a review
Admin pagesAdminsPhone number and a six-digit codeCheck payments, watch every stay, remind sitters, manage the team and prices
Sitter pagesSittersPhone number and a six-digit codeSee their own visits, post photo updates, read their reviews

Nothing secret ever reaches a phone.

The website only holds the public key. The secret key lives in a small Google Apps Script on PawinBali’s own account, which receives uploads, creates staff logins and runs on a timer: the calendar every 5 minutes, blocked days every 30, the bookings sheet every hour. Admins block a day by adding a “Full” or “Off: Ayu” event to the city’s calendar.

  • 0WhatsApp groups per booking
  • 2cities on one system
  • Rp 0monthly running cost
  • 6 hlongest wait for a photo

Petty Cash Backfill

Ten weeks of WhatsApp receipts, reconciled.

Client
ALL X, Bali operations
Role
Operations Manager; designed and ran it
Method
AI desktop automation, human checkpoints
Status
Reconciled; entry in progress
Rp1.043.000

in petty cash spend that existed only as forwarded receipts in a WhatsApp group. 39 ride and delivery receipts from 31 August to 9 October 2026 had never reached the ledger.

  • 39receipts found and verified
  • 10 wksof chat history searched
  • 5errors caught on re-check
  • 3 to 4 hof manual work replaced

Untracked spend by period

Rupiah and receipts
Tap a period for detail
TotalRp1.043.00039

What I built

Three systems the team already used, made into one record

Receipts arrived in a WhatsApp group. The ledger was a Google Sheet with a tab per month and a tab per person. Files belonged in month-dated Drive folders. Nothing connected them, so receipts sat in the chat until someone found time to scroll back.

The automation drove the WhatsApp desktop app directly, exported each receipt, and prepared a dated ledger row for it, with the file linked into the Receipt column as a chip.

  1. WhatsApp group
  2. Export receipt
  3. Drive, RECEIPTS / OCT 2026
  4. Ledger row and chip

The house rules

It followed the house rules already in the sheet

Categories, payment types, the DD/MM/YYYY date format and the tab layout were all read from rows the team had already written. The hardest rule was never written down: receipts print street addresses, while the team says nicknames. Matching the same address across different messages rebuilt that map, so later receipts filed themselves by address alone.

Five discrepancies a first pass missed

Receipt skipped entirely1
“Missing”, actually scrolled past2
Route misread from a caption2

Caught by re-checking every cluster boundary against WhatsApp’s document index, and the original PDF where a caption disagreed.

Human checkpoints

Two calls went back to a person instead of being guessed: a backlog of rides booked under an unfamiliar staff name, and two rides the ride app itself marked Profile: PERSONAL. Both were flagged and kept out of the ledger.

The time saved is measured against a teammate’s average DeskTime activity in Google Sheets for tracking these expenses, uploading receipts and updating the petty cash sheet by hand.

Under the hood

None of these builds needs a server of its own to maintain. Pick an action and watch where it goes, step by step.

Trace

    LayerAxiom Task ManagerKRIYĀ Studio AppPetty Cash BackfillLudwigPawinBali
    DatabaseGoogle Sheet: Tasks, Updates, Stages, Projects, Files, InboxGoogle Sheet: Bookings_Master, CRM, Income Dashboard, plus Requests, Quotes, Checklist and TasksGoogle Sheet ledger: month tabs + person tabsSupabase Postgres: 10 tables, all with row-level securitySupabase: bookings, clients, pets, photo updates, reviews, staff, prices, blocked days
    ServerGoogle Apps Script, runs as the company accountGoogle Apps Script: one web app serves three pagesNo server: AI drives the WhatsApp desktop appNo custom server: rules in the database, one edge functionGoogle Apps Script on PawinBali’s own account: uploads, staff logins, timers
    Front endMobile web app, add to home screenTeam app, public request page, private quote pagesThe WhatsApp group the team already usesVite web app on Netlify: student app + teacher pageOne web app on Netlify: booking, payment and pet pages; admin and sitter pages
    AccessTeam code, then pick your nameStudio code for the team; secret key in each quote linkRuns on the operations laptopEmail sign-up; the teacher approves each studentClients: a private link, no account; team: phone number and a 6-digit code
    FilesGoogle Drive, folder per stage and sideGoogle Drive, folder per clientDrive RECEIPTS folders by month, linked as chipsDecks and stories backed up to GitHub as filesGoogle Drive: pet photos and transfer screenshots, private to admins
    AIGemini: EN⇄RU translation, chat-to-task, with retry and a backup modelNone neededReads receipts; rebuilds the address-to-villa mapNone neededNone needed
    Automation5-minute check catches edits from any deviceCRM sync; emails on accepted quotes and offers; daily checklistsOne backfill run, re-checked against the chat indexSign-up creates a profile; spaced-repetition schedule; one-click backupCalendar every 5 minutes, blocked days every 30, Sheet copy every hour
    SafetyProtocol read-only; human edits never overwrittenLocked saves; rate-limited public forms; offers below the floor need the ownerUnclear items go to a person; personal rides flaggedPending sees nothing; students see only their own data; notes are teacher-onlyThe secret key stays on the server; sitters see only their own bookings; only admins see payments
    Running costNo per-user feesNo per-user feesNo new softwareFree tiersFree plans on PawinBali’s own accounts

    The same thread, other businesses

    How the Axiom and KRIYĀ setups adapt to other teams in Bali. Concept designs with sample data, not client work.

    07:00Reformer Pilates, 10 bedsFull, 3 waiting
    09:30Strength circuit, 12 spots5 open
    Pack10-class pack, 2 credits leftRenew
    21 dMembers not seen in 3 weeks7 to nudge

    Fitness and Pilates studios

    The KRIYĀ app already handles bookings by time and person, a code-protected team app, a public request page and a lapsed-client queue. For a gym, Pilates or yoga studio, the same engine becomes:

    • Class timetable with capacity and an automatic waitlist
    • Class packs and memberships that count down credits
    • Trainer schedules with the same clash check as artists
    • Check-in from the front desk phone
    • A “haven’t seen you in 3 weeks” queue with one-tap messages
    V3Pool pump noiseOverdue
    V1AC service, 2 roomsToday
    V2Linen, checkoutDone
    IDRVendor invoices3 due

    Villa operations log

    Staff report issues from their phones with a photo. Managers see every villa’s open jobs, who’s on it, and which vendor invoices are waiting.

    Milk
    Reorder
    Beans
    Low
    Cups
    OK
    OrderDraft to supplierReady

    Café stock and ordering

    Closing staff count stock on a phone. The system flags what’s low and drafts the next supplier order for the manager to approve.

    Works for teams in

    • Construction
    • Tattoo studios
    • Software companies
    • Villa management
    • Fitness studios
    • Cafés
    • Tutors and language schools
    • and any team with work worth untangling, whatever it runs on

    I seal the gaps your team has learned to walk around

    Four steps, and your team is using a real version well before the last one.

    1. The stakeout

      I sit in your chats, your sheets and your Monday meeting until I know where the work really goes. When in Rome… build as the Romans do, but better.

      Survey
    2. The wiring

      Your Google account, your folders, your numbering. I connect what you already have so updates travel without anyone chasing them.

      Thread
    3. The fitting

      A clickable mockup first, then the real thing on your team’s phones. They poke holes in it; I sew them shut.

      Build
    4. The handover

      A how-to guide in your team’s languages and one owner on your side who can run it without me.

      Launch

    House rules

    Ten rules every build follows. Short enough to remember, strict enough to matter.

    1. Build on what already works.
    2. Every number on the page must be checkable.
    3. If the team won’t open it, it doesn’t exist.
    4. Speak the team’s languages, all of them.
    5. Ask the person doing the work, not only the person paying for it.
    6. No new subscription without a very good reason.
    7. Fix the boring part first. It’s usually the expensive part.
    8. Write it down before you forget why.
    9. Leave the owner able to run it without me.
    10. Never automate a mess. Tidy it, then automate it.

    The oldest system on the island

    For about a thousand years, Bali’s rice farmers have shared water through the subak: a network of canals, cooperatives and water temples that decides who floods their fields, and when.

    In the 1970s the Green Revolution brought a new plan: plant as often as you can and ignore the temple calendar. Within a year or two the pests moved in and the water ran short.

    Years later, an anthropologist named Stephen Lansing ran the numbers. When neighbouring fields flood and go fallow together, the pests starve. The temple schedule had been doing the pest control all along, and it worked better than its replacement. The old way came back, and in 2012 UNESCO made it a World Heritage landscape.

    I build with that in mind. The system your people already run usually knows something you can’t see from outside, and my job is to give it better tools.

    What people ask first

    How much does it cost?

    It depends on the gap. If a build would cost more than the hours it gives back, I’ll tell you not to do it. You get a price after the first conversation.

    Do we have to switch software?

    No. Whatever your team runs on today, a spreadsheet, a group chat, an old CRM or a paper logbook, that’s what I build on. Nothing gets ripped out.

    How fast is fast?

    Ludwig went from a first question to a working teaching platform in a day. Bigger systems, like Axiom’s migration from a weekly meeting log, take a few weeks of real use and feedback.

    My team speaks three languages. Problem?

    Not for the app. It works in any language your team speaks, and translations never overwrite what a person wrote.

    Who owns it when you’re done?

    You. It lives in your Google account or your own Supabase project, not mine, with a guide your team can follow.

    When isn’t this a fit?

    When you want a forty-page strategy deck and nothing that runs on Monday.