Start a project

Software studio

Software built around your business, not the other way round.

Ligmu designs and builds custom software for companies: the internal platform your team runs on, the product your customers log into, and the integrations that hold both together. A small senior team, one phase at a time, and code that stays yours.

Discovery → working prototype in weeks, not quarters.

ENGAGEMENT / SHEET 01 REV. A Discovery 2 weeks, fixed Prototype clickable, real data Build 2-week slices FEEDBACK EACH SLICE Run it with you monitoring · fixes · next slice Hand it over your repo · your cloud · docs YOU OWN THE CODE AT EVERY STAGE No lock-in. No licence on your own product. Leave after any phase with everything that was built.

What we build

Four kinds of work, one team.

Most companies come to us with a process that has outgrown its spreadsheets, or a product idea that needs to exist before the market moves on.

Internal platforms

The system your team works in all day

Operations, admin, reporting and the workflows in between — replacing the spreadsheet-and-email layer that quietly runs the business.

  • Role-based access and audit trails
  • Dashboards people actually read
  • Migration from whatever you use today

Customer products

The product your customers log into

Web apps, portals and dashboards, from first screen to billing — built to be operated by your team, not only by us.

  • Accounts, billing and permissions
  • Design that survives real content
  • Analytics wired in from day one

Integrations

Systems that stop disagreeing

Payments, CRMs, messaging, telephony and whatever legacy service nobody wants to touch — connected so the numbers finally reconcile.

  • APIs, webhooks and event pipelines
  • Idempotency, retries and reconciliation
  • Clear failure handling, not silent drops

Rescue work

A project that stalled

A half-finished build, a departed developer, a system nobody dares deploy. We audit it, tell you plainly what it would take, and finish it if that is the right call.

  • Written audit with real options
  • Tests and deploys before features
  • Honest rebuild-or-repair answer

How we work

Four steps, each with something you can hold.

Every step ends in a deliverable you own, so you can stop after any one of them and still be ahead.

STEP 01

Discovery

We sit with the people who do the work, map what actually happens, and write down the scope, the risks and the price.

Ends with: a written plan and a fixed quote

STEP 02

Prototype

A clickable version with your real data in it, so decisions are made against something concrete instead of a slide.

Ends with: a prototype your team can try

STEP 03

Build

Two-week slices, each one deployed and usable. You see progress in the product, not in a status report.

Ends with: working software, in production

STEP 04

Run or hand over

We keep it running and keep improving it, or we hand it to your team with the documentation and access to take it from there.

Ends with: your call, either way

Capabilities

Boring, proven technology — chosen to fit the problem.

We pick tools your next developer will recognise. No framework of the month, and nothing that traps you with us.

Product & interface

  • React and TypeScript
  • Design systems
  • Dashboards and reporting
  • Accessibility and mobile

Platform & data

  • Node, Python, PostgreSQL
  • APIs and event pipelines
  • Payments and billing
  • Search and analytics

Running it

  • Cloud, containers, CI/CD
  • Monitoring and alerting
  • Backups and recovery drills
  • Security reviews

Engagements

Three ways to start.

Every one begins with discovery, because a price given before understanding the problem is a guess.

Discovery sprint

Two weeks to map the problem, prove the hard part is possible, and produce a plan with a real number attached.

Fixed price · fixed length

Build a product

A phase of two-week slices with a fixed scope and price per phase. You approve each one before it starts.

Priced per phase · most common

Embedded team

Senior engineers working inside your team, your board, your standups — for a set number of days each month.

Monthly · rolling

Questions

The things people ask first.

Who owns the code?

You do, from the first commit. It lives in your repository and deploys to your cloud accounts. There is no licence on your own product and no fee to leave.

How do you price work?

Discovery is a fixed price for a fixed two weeks. After that each phase is scoped and quoted on its own, so you always know the number before the work starts and can stop between phases.

How long until we see something real?

A clickable prototype with your data usually lands within the first month, and the first slice of production software follows within weeks of the build starting.

Can you work with our existing team?

Yes. We review with your developers, follow your conventions where they exist, and write the documentation as we go so nothing depends on us staying.

What happens after launch?

Either we run it with you — monitoring, fixes and the next round of improvements — or we hand it over with documentation and a walkthrough. Both are normal endings.

Start a project

Tell us what is slowing the business down.

Write a few lines about the problem and how your team handles it today. We reply with what we would build first, whether that is with us or not.

[email protected]

  • A reply from an engineer, not a form
  • No NDA needed for a first conversation
  • An honest answer if we are the wrong fit