SERVICES / 02
Focused engagements for building new software, getting a system ready to launch, or keeping it moving once it becomes business-critical.
Service modules · 01
Three ways to work with me — before your software exists, when it's about to ship, and while it runs your business. Fixed prices, closed scope, no meetings-by-default. Capacity is deliberately small and stated up front.
Build sequence
From idea to software in production. Fixed price, closed scope, one person owning the whole chain.
Launch sequence
Your software is about to go live? In one week I find — and fix — what would take it down.
Run sequence
Your senior software engineer, on subscription: one request at a time, async, pause anytime.
Why can a single engineer quote a fixed price? Twenty years across the whole chain — and a delivery pipeline I've heavily automated. That's the economics, not a slogan.
Protocol · 02
The things people ask before the first call — answered here so the call can be about your project.
I can't — that's what the scoping workshop is for. We spend half a day turning your idea into a written, closed scope: what's in, what's out, what "done" means. The fixed price is attached to that document, not to a guess.
It happens on almost every project, and it's fine: new needs go into a list. At the end of the sprint you decide if they're worth a follow-up sprint. What never happens is silent scope growth — that's how projects die.
You do, fully, on final payment: source code, repository, documentation, infrastructure configuration. Open-source components stay under their own licenses (I only use business-friendly ones).
The boring, proven ones that fit your problem — typically Django/Python or PHP (Symfony/Laravel) on the back-end, Angular on the front-end, PostgreSQL, deployed on your cloud or a simple VPS. You get a stack your next developer will actually understand.
Yes, heavily — that's part of why a fixed price is possible. I've spent years building an automated delivery pipeline, and AI assistance is one layer of it. Two things never change: I review and take responsibility for every line that ships, and your code and data never end up in anyone's training set.
Async by default: a shared board and a written update at least once a week. Calls exist, but they're the exception (kickoff, and when something genuinely needs a conversation). You'll always know where things stand without booking a meeting.
Yes. Everything ships with documentation and a handover session. If your team takes over afterwards, that's a success, not a problem — and I can stay available through Software Partner if you want continuity.
Deploy to production is part of the sprint, on infrastructure you own. After the 30-day bug guarantee you can run it yourself, hand it to your team, or move to Software Partner for continuous evolution.
Because one senior person doing the whole chain is the product. I run one sprint at a time and cap subscriptions at three: it keeps quality high and lead times honest. If the slot is taken, you get a date, not a maybe.
Trani, Italy — working remotely with clients across Italy, the UK and Australia for the past decade. Italian sole proprietorship, EU VAT, invoices you can actually put in your books.
Anything outside the written scope, content production, formal certified penetration tests, and 24/7 on-call. The bug guarantee covers defects against the agreed scope — a new idea is a new request, and that's a feature of the model, not a limitation.
