Turn your idea into a working application, not just a plan for one.
I design and build focused MVPs, AI tools and client portals for founders, creators and small businesses. You bring the problem and a clear picture of what a useful result looks like. Together, we define the right first version and I build it into something you can test, show and grow from.
The missing step between an idea and something people can actually use.
You probably already know what you want the application to do. The idea might live in a document, a spreadsheet, a Notion page or a collection of AI chats. What is often missing is the step between that idea and a product you can actually use.
Define the right first version
We start with the problem, the workflow and the result the application needs to create. From there, I help shape a realistic first scope around what matters most.
Build around the real workflow
The goal is not to add features for the sake of it. The first version should make the core workflow usable, testable and clear enough to learn from.
Work directly with me
You work directly with the person shaping, building and testing the product, without layers of account management or a large development team.
Working applications, not just concepts.
Different applications, different users and different workflows, built around a focused first version.
Conversion IQ
A conversion audit application with a structured multi-step scan, user accounts, payments, reports and admin functionality.
Audience Signal
A self-service audience research tool that turns real customer language into structured insight around pain points, desires and buying objections.
Wellness Compass
A coach-client portal with dashboards, check-ins, planning tools, client journeys, analytics and coach-facing workflows.
Nurtiva Care
A care-focused portal designed to bring caregiver information, daily logs, medications, appointments, tasks and care signals into one structured environment.
Focused digital products built around a real problem.
Not every business needs a large software project. Sometimes one well-designed workflow is enough to create something genuinely useful.
AI Applications & MVPs
Turn an application idea into a focused first version without trying to build every future feature at once.
- User accounts and dashboards
- Databases and structured workflows
- AI-assisted features where they improve the workflow
- Payments, reports and integrations
Internal Tools & Workflows
Replace fragmented manual processes with a digital tool designed around the way your business actually works.
- Assessment and intake tools
- Operational dashboards
- Reporting workflows
- Structured business processes
Client Portals & Platforms
Create a structured environment where clients or users can access information, complete actions and interact with your service.
- Client dashboards
- User roles and journeys
- Forms and progress tracking
- Member or service portals
From a useful idea to a focused working version.
Discover
We clarify the problem, the user and what the application needs to achieve.
Scope
We decide what belongs in version one and what can wait.
Build
I build the core application, workflows and required integrations.
Test
Important user flows are tested, corrected and refined.
Launch or Handover
The first version goes live, enters controlled testing or is handed over with the agreed next steps.
A working first version with a clear purpose.
You work with the person actually building the application.
I’m Hanneke Verhoef. I build the applications you see on this site myself, from shaping the first version and workflow through building, testing and refining the product.
I use AI-assisted development to move quickly from concept to working software, while still making deliberate decisions about scope, user experience and how the application should work.
That means you work directly with the person making those decisions and building the product, from the first conversation through to delivery.
Discuss your project →AI is part of the workflow, not the sales pitch.
I build with modern AI-assisted development tools because they let me prototype and iterate faster than a traditional workflow.
But “built with AI” isn’t the outcome you’re paying for. A working solution is.
AI goes into the product only where it genuinely improves the experience or workflow. The rest of the time the focus stays where it belongs, on the workflow, the user and whether the application actually works.
Clear project pricing, not open-ended hourly development.
Every application is different, but you should have an idea of the investment before starting a conversation.
Prototype or simple internal tool
For one focused workflow or a smaller first version designed to test the concept and create something genuinely usable.
Structured MVP or client application
For a focused MVP with more structure, such as user accounts, a database, defined workflows or selected integrations. Final pricing depends on scope and complexity.
More Complex application
For projects with multiple user roles, advanced integrations, AI functionality, payments, complex workflows or a broader product scope.
Before we start.
Do I need a complete technical specification?
A clear description of the problem, who the application is for and what you want it to achieve is enough to start. Turning that into a workable first scope is part of the project.
How long does a project take?
Focused projects are usually planned in weeks rather than open-ended development cycles. A small prototype may take a few weeks. A structured MVP with accounts, a database, payments or multiple integrations will take longer. The expected timeline is agreed before development starts.
Can we start with a smaller version?
In many cases that is the better approach. A focused first version makes it easier to test the idea, control the investment and discover what users actually need before expanding the product.
Do all projects include AI?
AI is used where it solves a useful problem. If normal application logic is the better solution, that is what should be used.
Will I own the application?
My goal is to make sure you are not dependent on me simply to access or operate your own product. Ownership, code access and the use of third-party services are documented clearly in the proposal. Where practical, important services are set up in accounts you control.
What happens after launch?
We agree upfront how changes should be handled after the first version is delivered or goes live. That can mean follow-up improvements, occasional support or a clean handover. It is decided per project rather than forced into a fixed retainer.
Who pays for hosting, APIs and external tools?
Any required third-party costs are discussed before development starts. They are normally separate from the development fee so you can clearly see both the cost of building the product and the ongoing cost of running it.
Tell me what you have in mind.
Tell me what you want to build, who it’s for and the problem it should solve. If it works as a focused first version, I’ll tell you what it would take to build. If it doesn’t, I’ll tell you that too.
Discuss your project