Get in touch

A software studio · Bangalore, India

Small problems,
done properly.

Most software is built for a market. These are built for a situation — a worship team at eight on a Sunday morning, a founder certain the right person messaged them a year ago, a nine-year-old whose school teaches in a language her parents do not speak.

See the four products
  • StudioFour products, four stages
  • FocusMobile · Web · Applied AI
  • Based inBangalore, India

01 / Approach

Three rules that survived contact with four products.

How the work gets decided.

  1. Start with one person, not one market.

    Every product here began with someone specific and a moment you could put a time on. MonkeyChords exists because a worship team’s chord app quietly stopped fetching songs and the workaround became a printer. One named person and one real Sunday settle more design arguments than a roadmap ever has.

  2. Say what is true.

    Everything below carries its actual stage — including the one that is still only a landing page, and the one that is still only foundations. No invented numbers, no borrowed logos, no screenshots of screens that do not exist yet. A studio that overstates four small things has nothing left to stake a large one on.

  3. Restraint is the feature.

    The hard part is rarely adding. Artos counts streaks but forgives a missed day, and refuses to rank friends against each other, because comparison would quietly ruin the thing it exists to protect. Knowing what a product must never do is most of knowing what it is.

02 / Work

Four products at four different stages. The stage is stated on every one.

Built for someone in particular.

What the stages mean

In beta
Real software, usable today, still changing
In development
Being built; not released yet
Validating
Testing whether it should exist at all
Early
Foundations built and tested; the product is not

Artos

Keeping a daily rhythm with God — and having it survive the week you miss.

Read the verse, write down what God spoke to you, name what you are praying for, and later find the answer written next to the prayer. A few friends can walk it with you: shared reading plans, a nudge to read or pray, a prayer chain that only grows when everyone prays.

Grace over guilt

The streak forgives a missed day rather than punishing it, and the friends layer encourages without ever ranking anyone. Habit apps normally run on the fear of losing something. The mechanic works, and it is the wrong one to point at someone’s prayer life.

Open Artos — opens Artos in a new tab

In beta

iOS · Android · Web

  • Expo
  • React Native
  • Firebase

Beacon

The right person already messaged you. You will never find them again.

Triage for X direct messages, for founders whose DMs are the company’s front door. Candidates, investors and partners all arrive in one inbox, and the good ones sink under the noise. The felt problem is not being behind on replies — it is regret.

Two axes, never one score

Fit is who someone is. Momentum is where the conversation stands. Blend them into a single number and you average away the one quadrant that matters — high Fit, no Momentum — which is the forgotten conversation the whole product exists to surface.

beacon.alakoda.com — opens Beacon in a new tab

Validating

Web

  • Astro
  • Cloudflare
  • Applied AI

MonkeyChords

One setlist has to serve a whole band, and no two people on stage read the same chart.

Import a chord sheet, transpose it, arrange the set, and play from the screen assuming both hands are busy: either outer third turns the page, a pedal works, and the screen locks so a brushed sleeve cannot lose your place. Prints two songs to a sheet for the mornings when paper is still easier.

A capo is a guitar’s control

A song in G with capo 3 is played as E shapes but still sounds in G — so handing the pianist a chart in E is simply the wrong chart. Guitar reads the shapes, everyone else reads the sounding chords, bass gets a bar chart, vocals get lyrics only. One setlist, four ways of reading it.

monkeychords.alakoda.com — opens MonkeyChords in a new tab

In development

Android

  • Kotlin
  • Compose
  • PDF export

Kannada Learning

Bengaluru schools teach Kannada. Many of the families in them do not speak it.

For children aged five to eleven who need Kannada for school and cannot practise it at home. Typography that scales with the child’s age rather than one size for everyone, and a syllabus keyed to the actual board rather than a generic curriculum.

What is actually built

The foundations and nothing more: design system, progress and streak engines, the entitlement model, the Kannada typeface bundled — built and covered by tests. The app itself is still a shell. It is on this page because it is real work, not because it is finished.

Early

Android

  • Kotlin
  • Compose
  • Firebase

03 / About

The studio is one person. That is a constraint, and it is on the page for the same reason the stages are.

One person.
Four products. No agency pitch.

Alakoda is run by Aaron Gunasingh, a data analyst and AI engineer in Bangalore, India. The day job is making operational data useful for engineering teams; this is where the small, stubborn things get built properly.

Being one person decides the work. Nothing here can be won by outspending anyone, so everything is won by knowing the problem better — which is only possible when the problem is one you or someone near you actually has.

04 / Contact

Have a small, stubborn problem?

A question about any of the four, a collaboration, or a conversation about work — they all reach the same inbox, and it is read by the person who builds the things.

founder@alakoda.com