Invoicing
Invoices in EUR or USD from Lazar Stanković PR DevLazar.
Sheet 1 of 3 · Work
DevLazar. A one-man shop for software that has to work on launch day.
Lazar Stanković PR DevLazar is the company behind the work, set up to take on clients abroad. I take a few commissions at a time and stay on them until the keys and the drawings are handed back. For larger builds I bring in a small crew I have shipped with before.
Station board
Station 03 · AuditOpen
OverallOpen
HoursCET
Detail A · The stations
Three ways to bring a build into the shop.
Station 01 · Project · AI-assisted
Proof of concept, MVP, product. In that order.
Build fast with AI first: a working proof of concept in days, so you can test the idea before you fund it. Then the MVP in weeks, scoped to survive the launch. Then the production build, with the AI-written parts read and rewritten by hand where it matters.
POCDaysBuilt fast with AI. Something you can click.
MVP3 to 8 weeksScoped to survive the launch.
ProductMonthsHardened, documented, handed over.
Each stage priced on its own
Station 02 · Retainer
Backend architecture and scale
Data pipelines, authentication, APIs under high-frequency load, the parts of a system that quietly decide whether it works. Node, NestJS, PostgreSQL, Redis, queues.
Station 03 · Fixed price
Launch Survival Audit
An inspection before your system meets its users. Load, failure modes, the parts that break first, and a written plan for what to fix in what order.
Fig. 2 · How a commission runs · Section viewOne job, start to finish, on a loop
01 · Intake
You explain the problem. I tell you whether I am the right person for it. Sometimes I am not, and I say so.
02 · Estimate
A one-page work order: what we build, what we do not, what it costs, when it lands. Signed before any code.
03 · Weekly cuts
Something runs every week. You see it, you steer it. No big reveal at the end.
04 · Handover
Your repo, your infrastructure, a runbook your next engineer can read, and the drawings. You own all of it.
Sheet 2 of 3 · Build logs
Case files, stamped by how much I can say.
NamedSector onlyRedacted
ProblemReal-time sports statistics and betting intelligence for fans who want data, not hunches.
I ownedBackend architecture: the data pipelines, authentication, and an API layer built for high-frequency consumption.
ProblemHigh-net-worth clients at managing portfolios and assets through a web application that cannot afford to be wrong.
I ownedSecurity-sensitive, performance-driven application work on . The client, the figures and the architecture stay under NDA. The log is stamped, not opened.
ProblemPatient and provider data scattered across providers that do not talk to each other. One ecosystem, secure, actionable, regardless of origin.
I ownedCore backend architecture and the communication layer between providers, plus the admin interface internal users lived in.
More logs in the cabinet: banking, insurance, IoT. Ask on the call and I will tell you what I can. References available from people who were in the room.
Sheet 3 of 3 · Working with a Serbian shop
The boring details, up front.
Contracts
A short services agreement plus your NDA, or mine. IP transfers to you on payment.
Hours
Central European Time. Full overlap with Europe, afternoons with the US East Coast, mornings with Asia.
The crew
One engineer, by default. For larger builds I bring in a small crew I trust and have shipped with before.
Bring it to the bench.
Custom software, an MVP, or a system that needs to survive its own launch. Fifteen minutes to find out if it is a fit.