Skip to content
TMLZEE
Low amber light grazing across the softly rounded edge of a dark timber bench top, the rest of the frame falling away into shadow.

Software product development

We build software products, and we show the joins.

TMLZEE GROUP LTD builds software products to order, from a workshop in Devon, incorporated in England and Wales under number 17061773. This page sets out how an engagement runs, what arrives in writing, and how to reach a person who will answer.

Start a conversation How we work

Company number 17061773

Company register entry

Registered name
TMLZEE GROUP LTD
Company number
17061773
Jurisdiction
England and Wales
SIC code
62012 (software development)
Macro photograph of a hand cut cairn joint in dark walnut and pale oak, the pins and tails meeting cleanly in warm side light.

The idea

Software fails at the joints, not in the middle

Most of the trouble in a software product is not in the clever part. It is at the seams: where a payment provider meets a ledger, where a mobile client meets an ageing back office system, where an assumption made in week two meets a regulation nobody read until week thirty.

A joiner cuts a cairn because the joint has to hold when the timber moves. We take the same view of software. Decide where the load will sit, cut for it deliberately, and leave the joint visible so the next person can see how it was made.

  • Interfaces written down before code is written against them.
  • Decisions recorded with the reason, not only the outcome.
  • Handover treated as part of the build, not an afterthought.

How an engagement runs

Five stages, and you can stop after any of them

This is the shape of the work we offer, written as commitments we are willing to be held to. Each stage ends with something in writing, so you can decide whether to carry on with the next one in front of you.

  1. A conversation, at no charge

    You describe the problem. We ask what you have already tried and what constraint is really binding, which is usually a deadline, an existing system, or a rule you have to satisfy. If we are not the right people we will say so in that call.

  2. A written proposal with a fixed scope

    Before any development begins you get a document setting out what will be built, what will explicitly not be built, the assumptions the estimate rests on, the price, and what happens if an assumption turns out to be wrong. If you do not want to proceed, the document is yours to keep.

  3. Build in short increments

    Work is cut into increments of roughly two weeks, each ending with something you can actually use rather than a status report. Source code lives in a repository you own or can be given at any point, not on a machine only we can reach.

  4. Review, then handover

    At the end we walk through the system with whoever will run it: how it is deployed, where the configuration lives, what breaks first under load, and what we would build differently with more time. That last part is written down too.

  5. Support, only if you want it

    Ongoing maintenance is a separate agreement with its own notice period. Nothing about the build requires you to keep us. A product you cannot take elsewhere is a product with a bad joint in it.

Plainly stated

Where the formal detail sits

Two things are worth knowing before you commit anything: what is on the public register, and what arrives in writing before an engagement starts. Both are set out here so you know where to look.

Officers and ownership On the register
Whoever directs this company, and whoever controls it, is listed against company number 17061773 in the Companies House record. Individual names are not copied onto this website, because the register is the authoritative source and it stays current in a way a web page does not.
Insurance and terms On request
Contract terms, professional indemnity position and data processing arrangements are provided in writing before any engagement begins, and are available on request beforehand. Ask by email and the documents themselves come back, rather than a précis of them.
An empty workshop interior at night, a single low pendant lighting a bare bench top while the room behind falls into deep shadow.

Where we are

Registered in Devon, working wherever the work is

The registered office is at Unit 15 Swift Industrial Estate, Kingsteignton, Newton Abbot, Devon. That address is the statutory one: it is where formal notices and post should go.

Development work is carried out remotely, with visits arranged when a project genuinely needs people in the same room, which is more often than the industry likes to admit. We are happy to travel for a kick off, a difficult review, or a handover.

The company works in English, contracts under English and Welsh law, and invoices in pounds sterling.

Next step

Tell us what you are trying to build

One email is enough to start. A paragraph about the problem, any deadline you are working to, and whether there is an existing system involved will let us give you a useful answer rather than a brochure.

[email protected] Every way to reach us

Email is the only route we monitor. Two working days is the target for a first reply, and a no arrives as plainly as a yes.