Good questions. Clear answers.

I work with individuals, creators, start-ups, small businesses and larger teams. What matters to me is that the software makes everyday work better: less repetitive work, an easier start or more possibilities for your business.

I enjoy building systems that many people use. I am just as happy creating a practical tool for someone running a business on their own, giving them more time for the work that matters.

I do not take on projects for far-right extremist organisations, the glorification of violence or propaganda. Party-political projects and political campaigns are also outside my area of work.

I want to build products that help people and businesses in everyday life. We can discuss openly in our first conversation whether your project is a good fit.

My main areas are tools for lead research and data collection, custom business software and financial tools. These include scraping tools, CRM systems, internal dashboards and financial workflow automation.

Depending on the task, the result may be a website, a web or desktop app, or a specialised AI agent. I connect the interface, data and workflows so the tool fits the way you work and takes meaningful work off your hands.

Tell me what you have in mind, the problem you want to solve and when you need a solution. The reason behind it is especially useful: what is slowing you down, what would you like to change, and what would make the project a success for you?

You do not need a finished technical specification. A clear description, a few examples or a look at your current workflow is enough to start. We can turn that into a concrete scope together.

Yes. The first conversation is free and comes with no obligation. We discuss your idea, the key requirements and your preferred timeframe. You can book a call directly through the website or send me a message first.

Afterwards, I estimate the work and prepare a proposal with the scope, price and schedule. You decide whether to proceed on that basis. The initial conversation does not commit you to a project.

A tightly defined project can be viable from around 16 hours of development. For a small product, I prefer to plan roughly 40 to 48 hours across several working days. That leaves room for implementation, testing, improvements and a final review with fresh eyes.

These are effort guidelines, not a fixed minimum price. Your proposal sets out what your project needs and what it costs. Individual changes to an existing application can also have a smaller scope.

I break the project down into features, interfaces, integrations and testing tasks. Experience with my own products and client projects helps me estimate the work involved and identify where technical uncertainty may need extra attention.

The proposal sets out the deliverables and assumptions, with time for testing and refinement. AI supports my development work, but it does not replace planning or checking the result. If an important unknown needs investigation first, I flag it before the project starts.

For fixed projects and agreed blocks of hours, my usual arrangement is 50% before work begins and 50% when the agreed scope is completed. This gives both sides a clear basis, including when working internationally. We can agree on different payment terms in writing.

An ongoing monthly arrangement is paid monthly under the contract. The 50/50 split does not apply to it. In every case, we agree on the scope, billing and payment terms before starting.

For a well-crafted website with a clearly limited scope, around 16 to 24 working hours is a useful starting point. For a prototype, custom application or desktop tool, I plan from roughly 48 hours. Complex features, detailed design, integrations and additional performance or security requirements can increase the work substantially.

Working hours and delivery dates are different things: feedback, content, access and coordination also affect the calendar. After our first conversation, you receive an estimate and schedule tailored to your project.

I can often start at short notice, depending on my current workload, sometimes on the day we agree the project or within the next few days. The scope and commission need to be agreed, with the necessary content and access in place. I confirm the actual start date in your proposal.

If something is urgent, mention it straight away or contact me on WhatsApp. I will check what I can fit in and which first step would help most.

During development, you see the actual progress through short screen recordings, screenshots, voice messages or working previews. You can give feedback early and see your idea become a product.

We agree on an update frequency that suits you. You can also choose the channel: WhatsApp, email, Slack, Microsoft Teams or another suitable tool. You communicate directly with me throughout.

Feedback is part of development from the start. I share work in progress so we can refine the design and functionality while changes still fit naturally into the process.

For a fixed project, agreed revisions within the defined scope are included in the plan. With a block of hours, feedback and implementation are tracked as time spent. If a request expands the agreed scope, we discuss the additional work and cost before I implement it.

I first check whether the request still fits the agreed scope. If it does, it can be accommodated within the project. If it requires additional work, I explain the estimated hours, cost and possible effect on the schedule before proceeding.

For example, a relatively contained extra feature might take around 8 to 10 hours; the actual task determines the estimate. With a monthly arrangement, we prioritise new requests within the agreed working time. Any additional capacity is agreed separately.

Yes. I can review existing applications, fix problems and continue unfinished projects. I first look at the code, the current state of the application and the outcome you want.

I can then recommend a targeted fix, a more substantial revision or a rebuild. I develop new products around the task at hand, and I do not replace an existing project without a good reason.

You receive the complete source code for the agreed project, the project files and the access needed to operate it. I walk you through the application, explain the main features and cover the next steps for running it. We agree on the level of documentation and training as part of the project.

You can then run the software yourself or have someone else develop it further. I can also provide hosting and maintenance if you prefer. Third-party components and external services remain subject to their own licences and terms.

I treat project information as confidential. AI-assisted development with tools such as Claude Code and Codex is also part of how I work. Project content may therefore be processed by the providers involved. We discuss any specific requirements for data, access and permitted services before starting.

If your requirements call for separate AI infrastructure, we agree on a suitable environment, potentially including an appropriate AWS Bedrock setup. Its configuration and data handling need to fit your requirements. Additional API and infrastructure costs are agreed upfront and are not automatically covered by my normal tool subscriptions.

Yes. I can host the application and its database, look after its operation and continue development after handover. We agree on the scope, ongoing costs and support arrangements for your project.

Smaller changes often fit into a modest block of time, for example around 3 to 5 hours. I estimate the work first and bill the agreed work under the chosen arrangement. If there is a service issue, you can contact me directly; specific response times are set out in the support agreement.

Contact me directly if something does not work as agreed after handover. I investigate the issue and distinguish between a defect in the agreed deliverable, a new request and later changes to the technical environment. Applicable warranty rights and agreed obligations to remedy defects remain in place.

New features, additional design requests and separate maintenance work are estimated in advance and billed as agreed. You can send me a message at any time; fixed support hours and binding response times are agreed explicitly. Careful testing is part of the plan, but I do not promise that any software will be entirely free of bugs.

Yes. I work under NDAs and respect agreed confidentiality requirements. If the fact that we are working together must remain confidential, I do not disclose that either. Client names, internal data and confidential functionality do not belong in my portfolio without permission.

If the agreement permits it and we have agreed on it, a carefully anonymised description can show the type of solution delivered. Even then, it must not reveal confidential information indirectly. Keeping the project entirely out of the public portfolio is also an option.

You work directly with the person who understands your idea, brings design and technology together and builds the result. My strength is combining creative problem-solving, practical product experience and a well-developed AI-assisted engineering workflow.

I get up to speed quickly, suggest practical solutions and show you something usable early. Short conversations and responsive communication keep the project moving. When a decision matters, I ask a focused question; you do not have to work out the technical implementation yourself.