Discuss your web app

Web apps

Your workflow, made usable.

The Caribeae schedule for one day, with classes in coloured blocks by teacher and the make-up spots left in each.SchedulingClasses, teachers and make-up spots
The Caribeae families list, with each family’s students, main contact and account balance.Family accountsContacts, students and balances
One family’s account in Caribeae: its credit, each child’s enrolment and rate, and the activity log.BillingBlocks, payments and credit
The Caribeae admin dashboard: classes today, new messages, overdue families, payments this week and a payments chart.DashboardWhat needs attention today
The Caribeae parent portal on a phone, showing a family’s credit and each child’s next class.Parent portalNext classes, on their phone
Parent billing in the Caribeae portal: the family balance, what each child is covered to and a receipt for the last payment.PaymentsBalance and receipts

Caribeae runs a swim school’s classes, billing and parent accounts.

View the case study

More web apps we’ve built.

The Now What module editor, with the admin menu for topics, courses, pricing, payments and users.Module editorWrite, save and publish lessons
A Now What course module as a learner sees it, with module numbers and a next button.Course viewWork through each module

Now What

Paid courses and free guides for people going through separation, with a custom editor for writing every module.

View the case study
The Flow Channels CRM dashboard with opportunity status, revenue and a sales pipeline funnel.

Flow Channels

Our CRM for service businesses, with contacts, pipelines, SMS and email in one place.

View the case study

A clear scope.
A working handover.

How we work out pricing

  1. Define version one

    Map roles, records and the essential workflow. Agree integrations, migration needs and acceptance criteria before the fixed quote.

  2. Try working software

    Review usable releases at agreed checkpoints, using representative tasks. Feedback shapes the next iteration within the agreed scope.

  3. Own the handover

    Agree source code, account access, data exports and documentation in the proposal. Launch support and later phases are scoped explicitly.

Before we get started.

How do we decide what belongs in the first version?

Start with the smallest complete workflow that is useful to a real user. We separate essential steps from later improvements, then agree what success looks like before building.

Can it connect to our existing tools?

Usually, if those tools offer suitable APIs or export options. We check access, limits and integration costs early. A difficult connection may need a separate discovery task.

Can different people have different access?

Yes. We define roles and permissions around who can see, edit, approve and export each kind of information, and test those boundaries as part of the build.

Can you move our existing data?

We assess sample files or the current system first. Data mapping, cleanup, trial imports and a cutover plan are scoped according to the quality and volume of the source.

Who owns the software, and can we release in phases?

Ownership, source code and third-party licences are set out in your agreement. We can plan phased releases, with a useful first version and separately agreed follow-on work. Hosting and ongoing support are separate.

Show us the workflow you want to improve.

Tell Joe and Hayden what you have in mind, who it is for and what needs to work. We’ll help you find a useful starting point.

Discuss your web app

Start with the work you need to improve.