LayConnect

Services

Senior engineering, from the first sketch to the on-call rota.

Four kinds of work, three ways to buy them, and a short list of the jobs we are the wrong studio for.

Service lines

What we are hired to do.

  1. 01

    Build

    We take a thing from the first sketch to the address it runs on, and we write the tests that keep it there. The people who design it are the people who deploy it.

    • Web platforms and customer-facing sites
    • Mobile apps, including right-to-left languages
    • Internal tools and admin platforms
    • Booking, scheduling and payment flows

  2. 02

    Rescue and modernise

    Systems somebody else built and nobody wants to touch. We start by finding the cause, not by proposing a rewrite, because a rewrite is usually the most expensive way to learn what the old system did.

    • Recurring outages traced to their cause
    • Performance work on slow pages
    • Hosting and platform migrations
    • Search visibility that was never set up

  3. 03

    Operate

    The part most studios hand back. We keep the thing alive: patched, backed up, watched, and changed when the business changes.

    • Hosting with one isolated service per application
    • Security hardening and access rules on every table
    • Uptime and integrity monitoring
    • Nightly encrypted backups

  4. 04

    Automate

    The standing manual work a small team does every week because there is nobody to hand it to. We hand it to software instead, with a safety gate wherever the answer matters.

    • Assistants that answer routine questions
    • Scheduled publishing
    • Appointment and follow-up reminders
    • Reporting that arrives without being asked

Engagement

Three ways to engage.

Pricing depends on scope, so we quote after the first conversation rather than publishing a number that would be wrong for you.

  1. 01

    Discovery sprint

    One to two weeks

    We read what exists, talk to the people who use it, and come back with options, risks and an estimate. The plan is yours either way: you can act on it with us, or hand it to anyone else.

  2. 02

    Fixed-scope build

    Four to twelve weeks

    Scope is agreed before the first line is written, and what is out of scope is written down beside it. You get one team, one deliverable, tested and deployed.

  3. 03

    Monthly retainer

    Three months minimum

    We run, secure and evolve what we built, or what you already have. Three months is the minimum, because anything shorter is a handover rather than an engagement.

Fit

Where this works, and where it does not.

This works well when

  • You need the thing built and then kept running, by the same people.
  • You inherited a system and cannot get it stable.
  • You need software in more than one language, including right-to-left.
  • You would rather have one team accountable than four suppliers pointing at each other.

This works badly when

  • You need twenty engineers starting on Monday.
  • The deadline is fixed and the scope is still moving.
  • The plan is to skip the tests to hit the date.
  • The work has to be done by people sitting in your office.

Questions

Asked often enough to answer here.

01How big is the team?
Small and remote, working across Europe, North America and Africa. The people who design and build your project are the people on call for it afterwards. If you need twenty engineers starting on Monday, we are the wrong studio.
02Why are your case studies anonymous?
Because a client's name is theirs. We describe every project by sector, country, the problem we were handed and the result, and we do not publish client names, domains, logos or people anywhere. Yours would be treated the same way.
03What happens if we want to take the work in-house?
You take it. Everything runs on infrastructure you control, the deployment steps are written down, and the tests tell whoever picks it up whether they have broken something. A discovery sprint is a plan you can act on with us or without us.
04Will you work on a system somebody else built?
Often. Rescuing inherited systems is one of the four things we do. We start by finding the cause of the failures rather than proposing a rewrite, because a rewrite is usually the most expensive way to learn what the old system did.
05Can you build in more than one language?
Yes. We have shipped in English, French and Arabic, including full right-to-left layout rather than mirrored text, and sites that choose a language from where the visitor is.
06How do we start?
Write to us and describe what is broken or what you want to exist. You get a reply from someone who would do the work. Most engagements begin with a discovery sprint of one to two weeks.

Start with a conversation, not a proposal.

Tell us the problem in your own words. If we are not the right studio for it, we will say so.

Start a conversation