Tell me what you are building.
What it has to do, who uses it, and when it needs to exist. You will get a straight answer about scope, price and timeline — or a referral, if it is not my kind of work.
Email is the fastest route and I read all of it. The short form below writes the email for you, in your own email app, so you keep a copy and can attach the thing you actually want me to look at.
Describe the project
Four questions, then your email app opens with the answers filled in.
Availability
- Status
- Available for new projects
- Working
- Remote · worldwide
- Overlap
- Agreed on the first callRather than assumed from a published figure.
Questions I get asked first
- How much working-hours overlap will we get?
- I work remotely with clients worldwide, and I would rather agree the overlap window with you on the first call than publish one here. How many hours actually need to overlap depends on how you want to run the work — a daily standup and a written weekly update need very different amounts — so it is worth settling early rather than assuming.
- How do engagements usually work?
- My preference is fixed scope: a call first, then a written scope before anything gets built, so we are both looking at the same description of the work. I also like to get a deployed staging URL up early and to send a written update each week, so you are watching the thing get made rather than waiting for a reveal. If the work is genuinely open-ended, a monthly arrangement may suit it better. Which shape fits is worth deciding on the first call.
- What do you charge?
- It depends on scope. As a guide, an AI product build typically runs $15k–$40k, and adding one AI feature to an existing product $4k–$10k. The price is in writing before work starts and holds unless the scope changes.
- Who owns the code and the intellectual property?
- You do. The code, the schema, the design files and the deployment setup belong to you, and the agreement we sign says so. If your company has its own contract or IP assignment, I'll work to yours.
- Will you sign an NDA?
- I have no objection in principle. One case study here is published anonymized — no client name, and only screens with the figures redacted — because the work sat on a firm's own financial statements and its production credentials, and my preference is to keep material like that off a public site whether or not anything obliges me to. Send yours over before the first call if you would rather talk under one, and I will read it.
- What happens after launch?
- How I like to finish a project: a documented repository, a walkthrough recording, and your own team on the accounts and infrastructure, so you are not dependent on me afterwards. What is actually delivered is whatever the scope we agree lists, so say if any of that matters to you and we will write it in. Staying on for support or further work is a separate arrangement rather than something bundled in.