LayConnect

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.

The work we take on.

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.

How we engage

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.

All selected work

We run what we sell.

Two products carry our name. Both are live, we are on call for both of them, and they follow the same rules as our client work.

  • The InvoiceFlow dashboard: the navigation down the left, the revenue and invoice counts for the workspace, and the most recent invoices.

    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.

  • The ManageFlow dashboard: the navigation down the left, the month's key figures, and the team's availability.

    ManageFlow

    Bookings, schedules and client records for a service business.

    Intake, booking, multi-resource scheduling, packages, deposits and role-based access, in one place.

Both products

How an engagement starts.

Every engagement takes one of these forms, and some move on to another.

  • Discovery sprint

    One to two weeks

    An audit, the options, and a plan you can act on with us or without us.

  • Fixed-scope build

    Four to twelve weeks

    One team, one deliverable, tested and deployed.

  • Monthly retainer

    Three months minimum

    We run, secure and evolve what we built, or what you already have.

Read the detail

What we hold to.

We turn work down when taking it would mean breaking one of these.

Boring tools where it matters
We pick tools that whoever maintains this in two years will recognise on sight. A new tool has a cost, and whoever maintains the code later is usually the one who pays it.
Privacy by default
We collect as little data as the job needs, store it encrypted, and put access rules on every table. Anything non-essential stays 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 run before every release. A release that fails them does not ship.

About the studio

Tell us what is broken, or what you want to exist.

The reply comes from the people who would do the work.