I don't bill by the hour or the day. Every engagement is priced monthly — based on what we're building, how long it takes, and how involved I need to be. The faster and better I work, the more value you get for the same price.
Book a call →Best for founders who have the vision — and maybe the designs — but need the senior technical person who turns it into a real, running system.
Testimonial coming soon.
Nicolas is an entrepreneur before anything else: he knows a company is only as good as its capacity to understand and deliver to its clients.
Best for founders who have a product and maybe a team, but need a senior technical brain on call — without the cost or commitment of a full-time hire.
While he may have had the highest hourly rate I've ever paid, he ended up costing me the least overall, due to his speed and effectiveness.
Fast, attentive, and professional — you can trust him with your eyes closed.
Best for companies that need a senior engineer who can take charge of the technical direction and be the strongest builder on the project. Two roles, one person.
Testimonial coming soon.
Best for founders and teams who have a specific, contained problem — and need it solved by someone senior, fast.
He gets it quickly. He delivers quickly. And he delivers quality.
Testimonial coming soon.
The better my tools get and the sharper my judgment becomes, the faster I deliver. A day-rate model punishes that — it means the more efficient I am, the less I earn. That's a broken incentive.
Monthly pricing aligns us on what matters: outcomes. You pay for what gets built, not how long it takes me. My speed and my AI-augmented workflow are my edge — and they're included in the price.
Every engagement is billed monthly at a flat rate. No timesheets, no day tracking. The monthly fee reflects the intensity and scope of the work, not the hours spent. Shorter, more intense engagements cost more per month. Longer commitments cost less.
Yes — and it usually does. Many of my Build engagements naturally expand into Lead as the project grows. That's a feature, not scope creep. We adjust the engagement model and pricing together when the work changes shape.
Yes. In Lead and Lead + Build engagements, I embed in your team, your Slack, your codebase. I work alongside your developers, not in a silo. For Build engagements, I can work solo or coordinate with designers and other contractors.
Typically 1–2 weeks from our first call, depending on current availability. Check the footer — if it says "Accepting new clients," I have capacity.
It starts with a 30-minute call where you tell me what you're building. I'll tell you which offering fits, and we'll scope the first milestone together. Most engagements start within 1–2 weeks of that call. You get weekly visible progress from day one.
That's what the call is for. Describe your situation, and I'll recommend the right fit. If your project doesn't match any of these offerings, I'll tell you that too — and point you somewhere better.
Everything. Code, infrastructure, documentation — it's all yours. I build for your autonomy, not for dependency on me. Every engagement ends with a full handover.
Each offering has a recommended minimum duration (shown above). For Solve engagements, there's no minimum beyond the project scope. For Build and Lead + Build, 3 months is the minimum. For Lead, 6 months — because meaningful technical leadership takes time to compound.
While he may have had the highest hourly rate I've ever paid, he ended up costing me the least overall, due to his speed and effectiveness. You need to see him code live to fully understand!
He gets it quickly. He delivers quickly. And he delivers quality. Communication is smooth, and he usually takes the time to make those small improvements that really make a difference in the final product.
He doesn't sugarcoat things. If you're doing something wrong, he'll tell you — and that kind of feedback is invaluable for entrepreneurs. His blend of business vision and coding talent makes him a key asset to any team.
30-minute call. No pitch deck. Just tell me what you're trying to build — I'll tell you how I'd approach it.