Skip to content
Novixa [Labss]

Work

Three you can open right now. One we can't show you.

What we built, the decision that shaped each one, and what's still in progress. Three of them you can open and use yourself right now, without asking us anything.

01Selected projects

Childcare · New Zealand

Yikes Nelson Tasman

Booking, payments, and admin as one system

Read the full story →

Live and taking bookings

Open the live site (new tab)

The problem

Out-of-school care runs entirely on scheduling: which child, which session, which venue, paid or not. They were holding that together across several paid tools that didn't talk to each other — paying for each one, and reconciling the gaps by hand. Parents felt the seams too, which matters when families are choosing who they trust with their kids.

What we did about it

We rebuilt it from scratch as one system rather than wiring the existing tools together more tightly. Tiered programmes, full-term subscriptions, and one-off sessions all run through the same booking flow with payment handled inline. The interface was redesigned alongside it — for a service parents choose partly on how credible it looks, the UI is not cosmetic.

What exists now

  • Public site and booking flow, built from scratch
  • Tiered programme selection — before-school, after-school, combined, and holiday programmes
  • Term subscriptions and single sessions through one checkout, paid via Stripe
  • Admin side for sessions, venues, and enrolments
  • Full UI and UX redesign

Monthly software bill

US$400–500 → US$25–50

What the subscriptions the platform replaced were costing them, against what it costs to run now.

Engagement extended — native Android and iOS apps are built and handed over. The store release date is the client's call.

The problem

Most workout trackers want an account, a connection, and a subscription — from someone standing between sets with cold hands and ninety seconds to spare. The interaction cost is the product: if logging a lift is fiddly, people quietly stop logging, and the app is worthless a fortnight later.

What we did about it

We built it local-first. Data lives on the device and is never sent to a server, which removes the account, the sync failures, and the privacy conversation in a single architectural decision. Automatic daily backups mean local-only doesn't mean fragile. Two screens, because it only needs two: log a lift, or look at what you've lifted.

What exists now

  • Workout logging designed around minimum taps mid-session
  • Dashboard for progress and training history
  • Local-only storage — no server, no account, no sync
  • Automatic daily backup exports, plus manual export and restore

Android and iOS builds are delivered — the client decides when they go up on the stores.

The problem

Inventory is almost never a greenfield problem. The stock data already matters, the systems around it already exist, and the business can't pause while someone replaces them. Most proposals here quietly assume a clean slate that doesn't exist.

What we did about it

Built to integrate rather than replace. The new system talks to the tools already in use instead of asking anyone to abandon them, and it was designed to roll out in stages so the operation keeps running throughout. Delivered ahead of the agreed timeline; currently going through implementation.

What exists now

  • Inventory management across the operation
  • Integrations with their existing software stack
  • Staged rollout, so nothing had to stop to switch over

The problem

A charity site has a harder job than a business one. It has about a minute to turn sympathy into a bank transfer, from someone who has never heard of you and has already been asked for money by three other causes this week. In India there's a second gate on top: individual donors want to see 80G before they give, because that's their tax deduction, and corporate CSR budgets won't move at all without CSR-1 on file. Most non-profit sites bury every one of those on a compliance page nobody scrolls to.

What we did about it

We put the proof where the doubt is. Registration number, 80G, CSR-1 and the auditor sit in plain view rather than two clicks deep — someone working out whether this is a real organisation shouldn't have to go looking. The giving flow leads with amounts tied to something you can picture instead of an empty box: ₹500 keeps a library open for a day, ₹1,000 funds one listening circle. Corporate CSR gets its own route, because that's a different conversation with a different person on a different timeline.

What exists now

  • Eight-page site — programmes, stories, events, and the giving flow
  • Donation flow with preset amounts tied to real running costs, plus a custom figure
  • Razorpay checkout, so no card details ever reach the foundation
  • 80G receipting for individual donors
  • Registration, 80G, CSR-1 and audit details surfaced on-page rather than filed away
  • A separate enquiry route for corporate CSR partnerships
  • A published quarterly ledger of every rupee in and out

02The wider remit

The kind of problems that land on our desk.

Four projects don't describe a whole studio. Here's the rest of what we take on.

  • 01

    AI agents that do the job

    There's a job in your business that runs on someone's attention — reading every incoming invoice, triaging support messages, chasing quotes, keeping two systems in sync. It isn't hard work. It's just constant, and it doesn't scale without hiring.

  • 02

    Custom software & apps

    Off-the-shelf software almost fits, so you bend your process to match it — or you run half the operation in spreadsheets alongside it. Both cost more than they look like they do.

  • 03

    Workflow automation

    The same twelve steps, every day, done by hand. Copy from here, paste there, send the email, update the sheet, tell the manager. Nobody's job description says this, but it eats the week.

  • 04

    Websites that earn their keep

    A site that loads slowly, says nothing specific, and gives a visitor no obvious next step isn't a marketing asset. It's a business card with hosting fees.

  • 05

    Bots

    The same fifteen questions arrive every week — order status, availability, opening hours, how to do the thing. Answering them is easy. Answering them for the four hundredth time is the problem.

  • 06

    Chrome extensions

    The fix your team needs sits inside a tool you don't control — a portal, a CRM, a supplier's website. A separate app to solve it means another tab, another login, and a habit nobody keeps.

03How we'd build it

Pick the closest thing to your problem.

The real phases, the parts that usually get difficult, and what you walk away owning. This is the conversation we'd have anyway — no reason to make you ask for it first.

Something your team does by hand, repeatedly, that software should be doing instead.

How it runs

  1. 01

    Watch it happen

    We follow the real process, not the documented one. Who touches it, in what order, and which steps exist only because someone once said so.

  2. 02

    Cut before we build

    Usually a few steps can just be deleted. Automating a step nobody needs is the most expensive way to keep it.

  3. 03

    Build the spine

    The core path first, running end to end on real data, with the edge cases visible but not yet handled.

  4. 04

    Handle the exceptions

    The messy 15% — bad inputs, missing fields, the supplier who sends a photo instead of a PDF.

  5. 05

    Hand over the controls

    You get logs, an off switch, and a way to see what it did. Automation you can't inspect is a liability.

Where this usually gets difficult

  • The real process turns out to differ from the described one — this is normal, and finding it early is the point of phase one.
  • One step depends on a human judgement that shouldn't be automated. We'd rather leave that step manual than fake it.
  • A system in the chain has no API and no export. Sometimes that's solvable, sometimes it changes the approach.

What you own at the end

  • The code and repository
  • The scheduling and logs
  • The credentials and accounts

No timelines or prices here on purpose — both depend entirely on scope, and quoting either before understanding your situation would be guessing.

Walk through mine

Want to see the one that isn't public?

We'll demo it on a call. And bring your own problem while you're there — you'll learn more from 15 minutes of us walking through how we'd approach it, including where it could go wrong, than from anything we could write about ourselves.