Skip to content
ANB Codes

Websites and apps

Online software and web apps

We build SaaS products and web platforms with the foundations they need from day one: secure sign-in, roles, billing, audit trails and an admin area, so new features don't mean a rewrite.

Overview

Software your customers sign in to and pay for, built to grow with you.

Software that customers sign in to and pay for has to be dependable in ways a prototype never is. Each customer's data must stay separate, permissions must hold, and billing must be right every month. Many early products struggle once real customers arrive, because those foundations were left for later. This service puts them in place from the first release.

Work begins with accounts, roles and the data model, because everything else depends on them. Core features are then built in two-week sprints, and you use the working product at the end of each one. We help you decide what a first paying customer truly needs and what can wait, so launch comes sooner and later features do not require a rewrite.

At handover there is a production platform, an admin console and API documentation, with the source code and accounts in your name once the project is paid. Our own invitation platform and a CRM for a study-abroad agency were built this way. Faults in agreed work are fixed free for 60 days, and development can continue on a care plan or with a dedicated team.

What you receive
Production platform · Admin console · API documentation · Source code and accounts
Typical technology
Next.js · TypeScript · Node.js · PostgreSQL · Supabase · Stripe

Who it's for

Is this right for you?

If an off-the-shelf tool already does most of what you need, we'll say so before you commit to a build.

  • A founder launching a subscription product that customers sign in to
  • A business whose early prototype struggles with real customers
  • A company turning an internal tool into a product it can sell to others

Scope

What goes into it

Every engagement is scoped to your goal. These are the parts most projects include.

  • Accounts and rolesSign-in, teams, permissions and single sign-on.
  • Subscriptions and billingPlans, invoices, trials and card payments.
  • Multi-tenant dataEach customer's data kept separate and secure.
  • Admin consoleManage customers, plans and settings.
  • ReportingDashboards and exports for you and your customers.
  • Public APIDocumented endpoints for integrations.

Timeline

How a typical project runs

Usual length: usually 10 to 24 weeks for a first version. Your written scope gives the exact plan.

  1. 01Weeks 1–3

    Accounts, roles and data model

    We set up secure sign-in, teams and permissions, and keep each customer's data separate from the start.

  2. 02Weeks 3–14

    Core feature sprints

    We build the main features in two-week sprints, and you try the working product at the end of each one.

  3. 03Weeks 10–18

    Billing and admin console

    Plans, trials, invoices and card payments go in, with an admin area to manage your customers.

  4. 04Weeks 16–24

    First paying customers

    A first group of real customers uses it, we fix what they find, then open it to everyone.

One-time project

A fixed quote for an agreed scope, paid in milestones. You own the code and accounts once it's paid.

Monthly care plan

A monthly subscription that keeps your software secure, monitored and improving, with response times in writing.

Getting started

What happens after you get in touch

Discuss your project
  1. 01Tell us the problemA short form or a call. A senior lead replies within one working day.
  2. 02One callWe sign an NDA first if you need one, then go through your goals, users and current systems.
  3. 03Written scope and fixed quoteWithin 48 hours of the call, with milestones and a timeline.
  4. 04Build in milestonesYou see working software at every milestone, and you own what we build.

Questions

Before you ask

What changes the size of the job

  • How many user roles and permission rules there are
  • Billing rules, such as trials, per-seat or usage pricing, and several currencies
  • Links to other systems and a public API for partners
Can you take over a platform someone else started?

Yes. We start with a code review, fix what's risky, then continue development.

Can we launch with fewer features and add more later?

Yes, and we usually recommend it. We agree a first version customers can pay for, then add features in later sprints.

How do you keep one customer's data away from another's?

Every record is tied to its customer account, and the database itself checks that rule on every request, not only the screens.

How is this priced?

As a one-time project with a fixed quote, agreed after a short call and paid in milestones. After launch you can add a monthly care plan for hosting, updates and support.

Tell us what you need built.

Share the problem in a few lines. After one call you'll get a written scope and a fixed quote within 48 hours.