Skip to content
Let's talk

Mobile and web apps for startups and growing businesses

Android and iPhone apps, and web apps for the jobs your spreadsheet has outgrown.

A delivery worker in a red uniform steadies a bicycle loaded with gas cylinders on a wet city street, between parked cars.
Refills going out in the rain.

The short version

We build Android and iPhone apps, and web apps like customer portals, dashboards and internal tools, for startups and small businesses in India and abroad. It starts with a free 30-minute call.

Who it's for
Businesses whose customers keep asking for an app, and teams running everything out of a spreadsheet and a few WhatsApp groups.
What you get
An app built around one job it does well, connected to your CRM or sheet, and published under your own developer accounts.
How it's priced
A fixed quote after the call, usually in three milestones: to start, at the first working version and at launch. If anything would move the quote, you hear first, in writing.

What we build

  • Android and iPhone apps

    For customers who come back every week: ordering again, bookings, loyalty points, tracking a delivery.

  • Customer portals

    Somewhere customers log in to see their own orders, invoices or progress, and download what they need.

  • Dashboards

    Your sales, stock and enquiries on one screen that keeps itself up to date.

  • Internal tools

    The order tracker, job sheet or approval flow your team runs on, as a proper tool with a login for each person.

  • Apps for teams on the move

    Site visits, deliveries, photos and signatures, recorded on a phone and synced back to the office.

  • An app with an assistant

    An AI assistant inside your app that answers from your own information, with a person one tap away.

    AI assistants for your business

What every app comes with

  • Cheap phones too

    Tested on real handsets, including a mid-range Android a few years old, because the simulator never shows you the lag.

  • Logins and roles

    Separate logins for customers, staff and owners, each seeing only what their role allows.

  • Your tools, connected

    Your CRM, sheets, payment gateway, WhatsApp or accounting software, so an order entered once shows up everywhere.

  • Store listings handled

    We prepare the screenshots and listing, and deal with Google Play and App Store review, which doesn't always explain its rejections.

  • Updates

    Fixes and new features go to a test build on your phone before they reach the stores.

  • Accounts in your name

    The developer accounts and store listings are in your name from day one. The code is yours once it's paid for.

How an app project runs

How a project runs: a call, a written plan with a fixed quote, a short demo every week so nothing comes as a surprise, the hand-over, and care afterwards if you'd like it.
  1. Map

    A 30-minute call, then a written plan and a fixed quote within two working days, listing the screens in the first version and the ones left out.

  2. Build

    Clickable designs first, then the build, with a weekly recorded demo and a test version on your phone once there's something to tap.

  3. Connect

    Logins, payments, notifications and your existing tools, wired in and tested on handsets before launch.

  4. Hand over

    The store listings go live, your team gets a walkthrough and written notes, and the first 30 days of fixes after launch are free.

When a website is enough

If what you need is a nicer way to show a menu, that's a website, and we'd build the website. It can still work like an app and sit on the home screen.

An app earns its place when customers come back weekly, your team lives in it, or you need offline use, the camera, location or notifications.

Small first, then grow it

The first version has the few things people will use every week, and nothing else. Once it's on their phones, what they tap picks the next features.

The wish list is kept, in case something on it turns out to matter.

Newer for us, built the same way

Apps are the newest thing we offer, so there are no app case studies here yet. If your app needs something we can't do well, we'll point you to someone who can.

Questions we get asked

Should I build an app or a website first?

A website, nearly always, set up so it installs to the home screen. A store app comes in when the phone itself is part of the job, like a customer reordering every Monday.

Do you build for both Android and iPhone?

Both, usually from one shared codebase, so they launch together and a fix lands on both at once. A few things, like some Bluetooth hardware, need separate work, and the plan says so.

Can you turn my website into an app?

Often you don't need to, since a website can install on a phone's home screen like an app. If you need a store app, we build it around your website's content and connections.

Who owns the app and its store listings?

You do: the Google Play and Apple developer accounts are opened in your company's name, and the code is yours once paid for. An app published under a studio's account is awkward to move later.

What happens when Android or iOS updates?

About once a year Apple or Google change something that needs a small update by a deadline. The optional care plan handles it; otherwise we quote for it when the store email arrives.

Does an internal tool need to be a phone app?

Usually not: most internal tools, dashboards and portals work well as web apps opened from a link. A phone app comes in when the job needs the phone itself, like a driver photographing a delivery.

More questions on the FAQ page

Tell us what the app should do

Describe the one thing the app has to do, in a sentence, and who'd open it. A photo of a paper sketch is a fine start.