Which path should I choose?
Shape a product if you’re still deciding what to build. Build an app if you know what it needs to do. Launch a website if you need a public site. Fix a workflow if your team is losing time to manual work. If you’re not sure, send a brief and I’ll suggest one.
Can you work on something that already exists?
Yes. I can improve an existing product, site or process without replacing the parts that already work.
Can you do design only, or build only?
Yes, though the best results come when design and build decisions stay close together, with one person making both.
What does it cost?
It depends on the scope, so every project starts with a short written scope and a fixed quote before any paid work. If it turns out bigger than one path, I’ll suggest a smaller first step.
What will it cost to keep running?
Hosting and tool costs are named before anything is built, and you approve each one. Many small sites and tools can run on free tiers. When one can’t, I’ll say so plainly.
Who owns it when we’re done?
You do. The code, the accounts, the domain and the data are in your name from the start.
What do you need from me?
A short brief to start, a call to walk through how the work happens today, and someone who can answer questions and test what I build. Please never send passwords or customer records in the brief.
Do you use AI? Is that safe for my business?
I use AI coding agents to build, and I review every change before it ships. Your data doesn’t go into an AI tool without your approval. If a feature uses AI itself, I’ll explain what it sends and where.
What happens if something breaks later?
You get written instructions with every handoff, and automated checks where a mistake would cost you. Ongoing support can be added to the scope if you want it.