This is how we work together.
You come with a problem. You leave with a solution.
On this page I walk you through, step by step, exactly how a collaboration with me unfolds — from your first message to the moment your product is live and working. No hidden fees. No surprises. No fine print hiding inside finer print.
The 5 steps
1. You write me.
Send a request through the form, or straight via WhatsApp, phone, or email — your preferred channel. It's free, no calendar widget, no account to create. I get back to you within 24 hours and we set a 30-minute conversation. Come as you are, with the problem already on your mind.
2. We talk.
You tell me what you want to solve. I ask questions — a lot of them, all to the point. I want to understand the real context of your business, not the surface symptom. No PowerPoint, no theatre. Two people, one conversation.
3. I recommend.
Once I understand the problem, I go away, do the homework, and come back with the right solution — plus the team that can deliver it, picked from my network. I tell you what should be built, why, with whom, on what timeline, and where the risks sit. Honestly.
4. We execute.
If you give the green light, I coordinate the whole delivery with the chosen team. You get weekly updates, direct access to the key people when you need it, and you never juggle five vendors in parallel. Your single point of contact stays me.
5. You pay on delivery.
You pay for the product only when the product is ready and works as agreed at the start. Not before. Not along the way. At the end.
The conversation costs time. The decision costs trust. The product costs money — but only at the end.
Why pay on delivery?
You've probably heard this story before: you sign a contract, hand over a sizeable advance, work begins, things drift mid-project, the money is already gone, and you're trapped in a project you no longer want — with an invoice you can no longer claw back.
I don't work that way. Paying on delivery means exactly what it sounds like: you pay when the product is ready, runs in your environment, and does what we agreed during discovery. Full stop.
That means the financial risk of the project sits with me and the teams I work with — not with you. You invest time (conversations, feedback, decisions) and trust. Your money stays in your account until the day the product brings you real value.
Yes, this model exposes me. If me or the team don't deliver, nothing gets paid — and the costs absorbed up to that point stay on my side of the table. But that's the bet I'm willing to make: if I pick good people, do serious discovery, and communicate transparently, projects land the way they should. Four years in IT have taught me this is the only way worth working.
And the most important part, for you:
If you cancel the project mid-way, you pay nothing. The costs absorbed up to that point are my problem, not yours.
That's the strongest promise I can make you — and it's the exact opposite of everything you've heard in the market so far.
What "free consulting" really means
This is where I want to be completely transparent, because "free consulting" usually smells like a catch.
I don't invoice you for our conversations. I don't bill hours. I don't bill discovery, analysis, recommendation, or the requirements document. The whole thinking phase — from our first call to the solution proposal — is on me.
How do I sustain myself financially? I work on a percentage from execution. That means the teams and partners I work with (developers, designers, agencies, financial partners) pay me a commission out of the value of the project they deliver to you. I bring them the right client — meaning you, with a clear, validated, well-documented need — and they recognize the value of that contribution.
It's a simple model. It's legal. It's clean. And it has one very important side-effect for you: I'm motivated to recommend the right solution, not the most expensive one. If I sold you an oversized project, you'd cancel mid-way (see the section above) and I'd be left with zero commission and the costs on me. That's not a trade I'd make against myself.
So yes, consulting is free for you. Not because "I give something for nothing", but because my business model means you're never billed for thinking — only for delivered work.
You don't pay for questions. You pay for a product that works.
1-year warranty included
Every software product I deliver comes with 12 months of maintenance and support, included. No separate invoice, no add-on package, no extra signatures. It's part of what you get.
What's included in free maintenance:
- Any bug that appears in the product is fixed at no extra cost, regardless of technology or complexity.
- Critical security updates.
- Small technical adjustments that keep the product running correctly: compatibility with OS, browser, or dependency updates.
What is NOT included in free maintenance:
- New features or scope changes — these are discussed separately as an add-on.
- Major design changes or rebranding.
- Infrastructure changes that come from your decision (e.g., switching hosting or migrating to another provider).
Why do I offer this guarantee? Because I trust the people I bring to the table. If the delivered product has bugs, fixing them is my responsibility — not yours to pay for.
1 year of maintenance and support, included. No surprises, no hidden invoices.
What's included in the product price
You don't pay separately for any of the stages below. All of them are included in the price of the final product:
- 1-on-1 consulting.
- Discovery and needs analysis.
- Requirements document.
- Wireframes.
- Interactive prototypes.
- UI design.
- Development (front-end, back-end, integrations).
- Testing and QA.
- Deployment into your environment (hosting, app stores, internal server).
- Basic training for your team.
- 12 months of maintenance and support.
All of this is part of the product. You don't pay extra for any of it. Period.
FAQ
How can consulting be free? What's the catch?
It's not a catch, it's the business model. I don't bill you for conversations because I get a percentage from execution from the teams and partners who actually deliver the product. That means you don't pay for thinking — you pay for the delivered product — and I'm motivated to recommend the right solution, not the most expensive one.
How is the final price set?
After discovery. In the first conversations I ask questions until I fully understand what you need, how complex it is, and which team fits. Then I come back with a written, clear offer for the final product — no vague estimates, no "from x to y". If the offer doesn't fit, you pay nothing and you're under no obligation to continue.
What happens if I'm not happy with the solution at the end?
During discovery we define together the concrete criteria the product must meet at delivery. If the product doesn't meet those criteria, it's not considered delivered — and you don't pay until it does. If dissatisfaction comes from new scope or features added later, we handle those separately. Open conversation is always on the table.
What does "delivery" mean for a software product?
Delivery means the product is deployed in your environment — hosting, App Store, Play Store, internal server, wherever was agreed — and functions according to the specifications we set together during discovery. Not "works on my laptop". Works on yours, in real conditions.
Can I change scope along the way?
Yes, but honestly. Small changes that don't shift the product's direction flow naturally. Big changes — new features, direction shifts, unplanned integrations — we discuss separately, transparently, as an add-on with its own scope and timeline. Nothing gets "tacked on" to the initial price without you knowing.
How long does a project typically take?
It depends on complexity. A presentation site can be ready in a few weeks. A SaaS platform or a custom ERP — several solid months. At the end of discovery I give you a realistic timeline, broken down by stage, not an optimistic sales date. I'd rather under-promise and ship on time than the reverse.
How do you pick the right team from your network?
Based on three criteria: experience relevant to your problem (industry, tech stack, scale), real availability within your timeline, and communication style. I work with people I've seen in action and would hire myself tomorrow. If my network isn't right for your project, I tell you straight — I don't force a fit that isn't there.
Who owns the code / product after delivery?
You do. All rights over the delivered product — code, design, content — belong to you after delivery and final payment. You receive the code, repository access, documentation, and credentials needed to operate the product independently, without me or the team that built it. The legal specifics are detailed in the contract.
What happens after the warranty year?
You have three options: continue on your own with your internal team (you have the code, you have the documentation); stay with the team that built the product through a direct maintenance arrangement; or come back to me and we discuss a new stage (new features, version 2.0, scaling). None are forced. After the 12 months, you're completely free.
Do you work with international clients?
Yes. I have 2+ years of experience with products built for the US market (REIvolution.io, SwiftMail, OverView) and I work fluently in English. For clients outside Romania we adjust the logistics (time zone, currencies, payment-on-delivery mechanics), but the core model stays identical: free consulting, payment on delivery, 1-year warranty.
Do you have a standard NDA?
I have a standard mutual NDA I can send before our first conversation, if you want to share sensitive details about your business. If you have your own NDA, I'll sign it without issues (after a normal review). Discretion is part of the job — I don't treat it as a favour.
How do I confirm you're the right person before signing?
The best test is the first conversation. It's free, you have nothing to lose, and within 30 minutes you'll know whether we speak the same language. On top of that: I can walk you through the products I contributed to (REIvolution.io, SwiftMail, OverView, RO platforms), connect you with a reference client, and put my initial recommendation in writing before any commitment. The decision always stays with you.
Ready for the first conversation?
You write me on your preferred channel — form, phone, WhatsApp, or email — and we set a 30-minute conversation about what you want to solve. You walk out with a clear direction. No obligations. No invoices. No pressure.
You come with a problem. You leave with a solution.