An engineering studio
with an editorial temperament.
LIT DEALS LTD is a software and infrastructure practice. We build custom applications, integrate systems, run cloud platforms and stay with the software long enough to keep it healthy. The company is intentionally small and takes on a limited number of engagements at a time.
- Discipline
- Software & infrastructure
- Model
- Small, senior teams
- Language
- English
Software you can live with.
Our attention is on long-lived systems: the internal platforms, customer-facing products and integration layers that a company still depends on five years after they were first written. Those systems reward patience — clear architecture, meaningful tests, a deployment pipeline that is boring on purpose.
We work across web, cloud and data. What ties the work together is not a specific stack, but a certain temperament: precise, calm, accountable, and honest about trade-offs.
We pick boring on purpose.
Every decision — a language, a database, a queue — is a decision future engineers will have to live with. We prefer widely understood, well-supported technology over the currently fashionable one, and we reserve novelty for the parts of the system where it earns its cost.
We use managed services when the maintenance burden of self-hosting outweighs the savings. We use custom code when a platform would force us into an awkward shape. We're happy to explain, in writing, why any particular piece exists.
None of this rules out modern tooling. It only rules out chasing tools for their own sake. A codebase that a competent engineer can be productive in within a week is more valuable than one that flatters the résumés of its original authors.
Small teams, senior hands
The engineers writing the code are the ones you meet in the first conversation. There is no delivery hand-off.
Written thought
Architecture notes, decision records and clear briefs make it possible for the next person — including us, six months later — to understand why.
Reversible steps
Feature flags, staged rollouts and small pull requests. We ship in slices thin enough to undo.
Long support horizons
Our maintenance work is deliberate: monitoring, patch cycles, roadmap reviews. We do not disappear at launch.
Plain-language honesty
We explain trade-offs without jargon and recommend against work we don't think is a good use of a client's budget.
Care for the craft
Code is a text people read. We treat it accordingly: named clearly, structured for the next reader, revisited when it stops making sense.
Partnership, not throughput.
We do our best work when we are close to the people who use the software — operators, founders, engineering leaders. That proximity shapes how we run engagements: weekly working sessions, open access to the codebase from day one, and quarterly reviews that treat the roadmap as a living document rather than a contract to be enforced.
We are comfortable embedding into existing teams, leading a greenfield build, or being the small engineering group behind a non-technical founder. The shape changes; the standard of care does not.
Quality as a daily practice.
Quality, for us, is not a review at the end of a phase. It is a way of working: peer review on every change, tests that describe behavior in plain terms, environments that mirror production, incident reviews that focus on the system rather than the individual.
We measure ourselves on a few concrete things: how quickly a new engineer can make a safe change, how easy it is to reproduce an issue reported from production, and how confident the team feels deploying on a Friday afternoon. When those numbers move in the right direction, most other things follow.
Design for the third year, not the third week.
A product that scales is one whose team can still change it without fear. We plan capacity, but we also plan for the humans who will maintain the system: onboarding docs, clear service boundaries, observability that answers real questions, dependency hygiene that keeps the codebase moveable.
Scale, in that sense, is a human property before it is a technical one.
