Software studio
We build the software, then we stay and run it.
We are a small remote team. We design and build web platforms, mobile apps and internal tools for the people who will live with them, and we ship and operate two products of our own.
What we do
Four kinds of work.
Most of what we are asked for falls into one of these. A project often starts in one and ends in another.
Build
Web platforms, mobile apps and internal tools, from the first sketch to the address they run on.
Rescue and modernise
Systems inherited from someone else: outages, slow pages, abandoned payment flows, migrations nobody wants to start.
Operate
Hosting, security hardening, monitoring, backups, and the steady stream of changes that arrives after launch.
Automate
Assistants, publishing, reminders and reporting that take standing manual work off a small team.
Selected work
Six projects, described by what changed.
Our clients' names are theirs, not ours to advertise. Each project is given by sector, country, the problem we were handed and the result.
One clinic, one stack, one team on call
Bookings, intake, follow-up and marketing were spread across disconnected tools. Now they are one stack the clinic owns.
An inherited booking portal, made stable
Recurring outages, slow pages and abandoned payment flows on a site built by someone else.
From a paper flyer to a live service in days
No website, a paper flyer, and an urgent need to hire carers and reassure families.
A rewards loop residents can trust
Residents declare plastic waste for pickup and earn rewards, with collectors, controllers and administrators each doing their part.
A trilingual site, and two interns who can ship
An outdated site, a set of real photographs going unused, and two interns who needed to learn how work gets shipped.
Back online before the purge deadline
A business site sitting on an expiring hosting plan, days away from being deleted.
Our own products
We run what we sell.
Two products carry our name. Both are live, both are ours to fix at two in the morning, and both are held to the same rules as client work.
InvoiceFlow
Invoicing for small businesses, with a paper trail.
Multi-tenant invoicing: invoices, client history, signature requests, and a signed receipt stored against every invoice.
Read about InvoiceFlowManageFlow
The day-to-day operating system for a service business.
Intake, booking, multi-resource scheduling, packages, deposits and role-based access, in one place.
Read about ManageFlow
How we engage
Three ways to start.
Every engagement is one of these, or one of these followed by another.
Discovery sprint
An audit, the options, and a plan you can act on with us or without us.
Fixed-scope build
One team, one deliverable, tested and deployed.
Monthly retainer
We run, secure and evolve what we built, or what you already have.
How we work
Four commitments.
These are not aspirations. They are the reasons we say no to some work.
- Boring tools where it matters
- We pick tools that whoever maintains this in two years will recognise on sight. Novelty is a cost, and it is usually paid by someone who is not in the room when it is chosen.
- Privacy by default
- Least data collected. Encrypted storage. Access rules on every table. Nothing kept that does not need to be kept, and anything non-essential switched off until someone asks for it.
- One team, from mockup to operations
- The people who build it are the people on call for it. Nobody hands your system to a support desk that has never read it.
- Everything tested
- Accessibility, security headers and end-to-end checks gate every release. A release that cannot pass the gate does not ship, and a gate that does not block is not a gate.
Tell us what is broken, or what you want to exist.
One reply, from the people who would do the work. There is no sales desk in between.
Or write to contact@layconnect.com