SeptiConnect

How we built it

1. 1

   An introduction through RTM Works

   The founder came to us through RTM Works, part of RTM Manufacturing, which we've built for since November 2025. They had worked in the field for years, and the existing tools they used weren't doing the job, so they decided to build their own product.

2. 2

   Scoping workshops

   Before any code was written, we ran a series of workshops with the founder to understand where the product sits: who uses it, what each person needs to see and do, and which device readings matter. Technicians needed to report issues from site, and admins needed to see every report, get an alert and follow each one through. The workshops ended with a written scope for the first version.

3. 3

   Proposed solutions

   We came back with 3 ways to build it: a web app on its own, a web app with a separate mobile app for technicians in the field, or a progressive web app that installs on a phone like an app. The founder chose a web app built to work well on phones, because one app let us release changes faster and keep improving it in small steps.

4. 4

   Hosting on AWS

   We set up the AWS accounts SeptiConnect runs on and the infrastructure inside them. The app runs in containers on Amazon ECS behind load balancers, with AWS Lambda functions alongside it.

5. 5

   Development

   We built it in 5 stages. The finished product has 3 parts: a dashboard showing flow rates, pressure levels, pump status and water levels from every connected device, the forms technicians fill out on site, and the alerts and tracking for admins. Throughout, the founder followed progress the way every client does: a preview link to click through, regular check-ins and written updates.

6. 6

   Testing rounds

   We ran several rounds of testing, and 3 groups tested it: our team, the founder's team, and an independent tester who hadn't worked on it. An outside tester catches what the people who built it, and the people who asked for it, are too close to see.

7. 7

   Delivery and handover

   SeptiConnect went live once testing was done. Nothing was switched on until it had been running and tested, the rule we follow on every build. Handover included training for the founder's team, support through go-live, written guides, and a support procedure so they know how to raise a problem.