S/01
Custom Software
Applications built from the domain up, in languages and frameworks chosen for the next decade — not the last one.
Vol. I · Issue 01The Practice · Software & Infrastructure17 July 2026
A software practice — Est. digitalSystems that carry weight,
Systems that carry weight,
designed to be maintained.
LIT DEALS LTD is an independent studio for custom software, cloud platforms and integrations. We take a small number of projects, write the code ourselves, and stay long enough to keep them healthy in production.
- Focus
- Long-lived software
- Model
- Small teams
- Method
- Ship & steward
Custom Software✦Cloud Platforms✦System Integration✦Web Applications✦APIs✦Legacy Modernization✦Quality Assurance✦Consulting✦Custom Software✦Cloud Platforms✦System Integration✦Web Applications✦APIs✦Legacy Modernization✦Quality Assurance✦Consulting✦
01 — The PracticeA studio,
A studio,
not a factory.
We build software the way a good workshop builds anything worth keeping — slowly, deliberately, and with the people who will use it. Most of what we ship is invisible: internal tools, back-office systems, integrations that let other software finally speak to each other. It is the plumbing of a business, and we take it seriously.
LIT DEALS LTD works with founders, operators and engineering leaders who want a technical partner rather than a vendor. We are deliberately small. A project has a lead engineer who owns it end to end, from the first workshop to the fifth quiet quarter after launch when nothing breaks and everything simply works.
02 — Services
Core disciplines.
A concentrated set of services chosen because they compound. We do not chase trends; we deepen what already works.
S/02
Cloud Platforms
Infrastructure as code, container orchestration and pipelines that make deployment routine instead of eventful.
S/03
System Integration
Bringing ERPs, CRMs, payment gateways and internal services into a single, observable narrative.
S/04
Web & Digital Products
Customer-facing surfaces designed for performance, accessibility and search — the way the modern web expects.
S/05
Modernization
Careful refactors, incremental rewrites and language migrations that keep the business running throughout.
S/06
Quality & Support
Automated testing, staged environments and long-term maintenance contracts that make software a living thing.
03 — Method
How the work happens.
- 01
Discover
A short, intense phase of interviews, architecture sketches and constraints. The output is a written brief we both sign.
- 02
Prototype
The riskiest slice built first, in production-grade code, so decisions are made against something real rather than a slide.
- 03
Build
Weekly demos, small pull requests, continuous deployment. Nothing accumulates unseen for a month.
- 04
Operate
We stay: monitoring, incident response, quarterly reviews and roadmap conversations for as long as it makes sense.
04 — Belief
"Good software is a quiet inheritance. It arrives without ceremony, saves someone hours every day, and is still there, still working, when the team that built it has long since moved on."
— House principle, LIT DEALS LTD
05 — Problems we take
The kinds of things that land on our desk.
We tend to be called when the spreadsheet has become load-bearing, or the platform that carried the company through year three is starting to strain in year five.
- An internal tool everyone depends on but no one can safely change→ New internal platform
- Two systems that should share data and don't→ Integration layer
- A public product that must move from prototype to reliable service→ Productionization
- A monolith that has quietly become three products→ Extraction & modularization
- A codebase whose original authors have moved on→ Modernization & handover
- A launch window with no time for surprises→ Delivery partnership
06 — Capability
Infrastructure with intention.
We treat infrastructure as a first-class part of the product. Environments are reproducible, deployments are observable, and the path from a developer's laptop to production is a single, boring pipeline that behaves the same at 03:00 as it does at 15:00.
Cloud native
AWS, GCP, Azure and self-hosted stacks. Kubernetes when it earns its place.
Data & storage
Relational and document stores, message queues, warehouses, caches — chosen per workload.
Observability
Structured logging, metrics and traces wired in from day one, not bolted on after an incident.
Security posture
Least-privilege access, secret management, dependency scanning and sensible default hardening.
07 — Fields
Industries we can support.
We are generalists by training and specialists by engagement. These are the environments we tend to feel at home in.
F/01Financial services
F/02Logistics & mobility
F/03Retail & commerce
F/04Media & publishing
F/05Healthcare technology
F/06Manufacturing
F/07Professional services
F/08Education & research
08 — Toolkit
The tools we reach for first.
Choices are made per project, but these are the technologies our engineers know deeply and default to when there is no reason to do otherwise.
Languages
TypeScript · Python · Go · Rust · Kotlin
Frontend
React · Next.js · TanStack · Svelte
Backend
Node.js · FastAPI · Django · gRPC · GraphQL
Data
PostgreSQL · Redis · Kafka · ClickHouse · BigQuery
Cloud
AWS · Google Cloud · Azure · Cloudflare
Platform
Docker · Kubernetes · Terraform · GitHub Actions
09 — Standards
Quality is a habit, not a phase.
Written first, spoken second
Every meaningful decision lives in a document a new engineer can read a year from now.
Tests as evidence
Automated tests exist to prove behavior, not to hit a coverage number. We write the ones that pay their rent.
Reversible by default
Feature flags, staged rollouts and clear rollback plans. A deploy that cannot be undone is a deploy we don't do.
Ownership beyond launch
The engineer who built it is the engineer who is paged when it misbehaves. That focuses the mind wonderfully.
10 — Security & Scale
Built to grow without breaking.
Security is treated as a design constraint, not a review at the end. Access is scoped, secrets are managed centrally, dependencies are watched, and sensitive paths are audited. We assume that anything worth building is also worth attacking, and we design accordingly.
Scale is handled the same way. We prefer boring, well-understood patterns — clear service boundaries, idempotent operations, queue-first workflows, cache invalidation you can actually reason about. When something must be exotic, we document precisely why, so the next engineer inherits a decision rather than a mystery.
11 — Why LIT DealsThe team that builds it
The team that builds it
is the team that keeps it running.
- Direct access to senior engineers on every call.
- Fixed teams — no rotating cast of subcontractors.
- Written architecture decisions, not verbal ones.
- Weekly working demos over monthly status decks.
- Long-term maintenance treated as first-class work.
- Honest recommendations — including 'don't build it'.
12 — Questions
Frequently asked.
How do engagements typically start?＋
With a short discovery conversation over email, followed by a paid discovery week if the fit looks right. The output is a written brief and a fixed proposal for the first phase.
Do you work on fixed price or time and materials?＋
Both. Discovery is fixed; delivery is scoped in short milestones. Long-term maintenance is a monthly retainer. We choose whichever removes the most ambiguity for the client.
Can you work with our existing team?＋
Yes. Many engagements are embedded, with our engineers pairing with in-house developers, sharing patterns and gradually handing over ownership.
Do you sign NDAs before discovery?＋
Yes, as a matter of course. Everything discussed with a prospective client is treated as confidential from the first message.
Where are you based, and do you travel?＋
We operate remotely by default and travel for kick-offs, key workshops and critical launches when it clearly helps the work.
What happens after launch?＋
We stay. Every project we ship has a monitoring plan, an on-call arrangement and a quarterly review. Software is an ongoing relationship, not a delivery.
13 — Correspondence
Write to us.
Whether you have a brief in mind or a problem you can't quite describe yet, a short email is the best place to start. We reply to every serious enquiry.
- Company
- LIT DEALS LTD
- kellymarti84@gmail.com
- Website
- litdealshub.com
