MVP and custom software development
An MVP should prove your idea with real customers, not just in a demo. I build the smallest version worth launching on a foundation you won't have to throw away.
Small doesn't mean rough. Security, speed, accessibility and tests are built in from the first release.
- Pricing
- Estimated per project
- Where
- South Florida or remote
Small, but ready for real customers
Security
Sign-in, permissions and input checks done properly, secrets kept out of the code, and dependencies kept up to date.
Performance
Pages that load fast on a phone, and database queries that hold up as your customer list grows.
Accessibility
Built with WCAG 2.2 AA as the target, so people who use a keyboard or a screen reader can use it too.
Reliability
Automated tests, monitoring, backups and a way to roll back a bad release.
Privacy
Collect only the data you need, and protect what you keep.
Room to grow
Clear, documented code on well-known tools, so the next feature isn't a rewrite.
A vibe engineer, not a vibe coder
I use AI every day, but I decide how the software works, and I check every change before it ships.
Vibe coding means asking an AI for an app and shipping whatever comes back. It gets a demo running fast, and it often leaves code nobody understands. As a vibe engineer, I tell the AI exactly what to build, then review every change for security, data handling and edge cases.
What a build can include
Accounts
Sign-in, user accounts and roles.
Payments
One-time payments and subscriptions.
Integrations
Connections to the tools you already use, like accounting, CRM and email.
Admin screens
Tools for your team to manage customers, content and settings.
AI features
Only where they help. See AI integration.
Tools I use
Usually TypeScript, React and Next.js in the browser, and Node.js with PostgreSQL on the server, hosted on AWS or Azure. I choose well-known, well-supported tools so it's easy to find people to maintain them.
From my recent work
- A production-ready MVP
- For an AI data startup, I took the first version from idea to production, with security checks, monitoring and repeatable releases built in. It moved into marketing and was shown to executives at major companies.
Common questions
- How much does an MVP cost?
- Every build is estimated up front. After we talk through what you need, I'll send a written estimate for the first version, so you can adjust the scope before you commit. Work is billed hourly in prepaid blocks, and I re-estimate the rest after each one.
- How long does it take?
- It depends most on how finished it needs to be. A rough proof of concept can come together quickly. A production-ready first version with the core features takes longer, and a full application with every edge case, integration and automation takes longer still. Off-the-shelf tools can shorten any of these. I estimate yours up front and update it after each block.
- Why not a fixed price?
- Plans change once real people use the product. Billing by the hour lets you change priorities between blocks, and you always see where the budget stands.
- Who owns the code?
- You do, once it's paid for. Your product lives in your own code repository and accounts from day one. I keep the general tools and know-how I bring to every project, and you get a permanent license to any of those that end up in your product.
- Can you take over a project someone else started?
- Yes. I start with a review so we both know what's there, then we decide whether to fix it or rebuild it.
- What happens after launch?
- I can keep improving it, help you hire a team, or hand it to your developers with documentation.
- Do you use AI to write the code?
- Yes, where it helps. On a build like this, I review AI-written changes myself, and they go through the same tests and security checks as the rest of the code before they ship.
- Will you sign an NDA?
- Yes. I'm happy to sign a standard NDA before you share the details.
From first message to launch
Tell me about it
Send a few sentences about what you want to build.
I'll ask questions
About your users, features and must-haves. Answering them often sharpens the plan on its own.
Free call
If it looks like a good fit, we flesh out the plan together on a free call. If there's an easier or cheaper way, or I'm not the right fit, I'll tell you.
Written estimate
I send the scope of work and an estimated cost. We adjust it together until it fits your budget and covers the smallest version worth launching.
Design
I write down the data, integrations, hosting and security in plain language you can review.
Build in blocks
You prepay a block of hours. I build in small pieces you can try as they land, and after each block we review what's built and re-estimate the rest, so you see how the budget is tracking before you commit more.
Launch and hand off
Put it in front of real customers, watch how they use it, and adjust. Then documentation, tests and help hiring the people who will take it over.
Tell me what you're working on.
A few sentences is enough. I'll reply within one business day with questions or a next step.