You write.
Answer one structured set of questions in a single sitting. We reply within one business hour.
You went out on your own. Your website should look like you meant it.
You know your craft. What you need now is a credible home for it online: your services, your story, a way for clients to reach or book you. We build it with AI agents, then hand over the code, pipeline, agent skills and training to keep building it yourself. No agency retainer, no developer on speed dial, no invoice for changing a price.
A one-person practice needs three things from a website: it has to look credible, clients have to be able to reach or book you, and it must not turn into a running cost or a dependency. The two obvious routes each fail one of the three. A do-it-yourself builder gives you something today, then leaves you spending evenings making a template almost work. An agency builds it properly, then every price change becomes a ticket and an invoice. We finish the hard parts, then hand you the powers to continue: the site, the code, the pipeline, and an AI agent configured to make changes for you.
Everything in this track is one of the standard website packages - most often the landing page or the business site shape - scoped for a one-person practice and quoted without a call. Fixed scope, fixed price, full handover.
From first email to flying solo. Four steps. Everything important stays in writing.
Answer one structured set of questions in a single sitting. We reply within one business hour.
You receive a fixed scope, fixed quote and payment path. Work starts after the deposit and your content arrive.
Your first working draft arrives within 5 working days. If it does not fit the agreed brief, we refund the deposit in full and the engagement ends.
We launch, hand over the repository and pipeline, give you the playbook, and train you live.
Payment has three stages: deposit before work, payment on first-draft acceptance, and final payment on handover.
See how our staged payments work - the whole process, the safety model and every boundary, in writing.
Experts who have gone independent, or are about to.
An honest word about timing. Many people going solo right now are doing it because AI is reshaping the job they used to have. If that is you, here is the useful part: the same shift is what makes a professional website manageable for one person. You describe changes in plain language, an AI agent writes them, and an automated pipeline checks every result before it goes live. Someone still has to set that up around your work and show you how to steer it. That is our job here, for exactly one project, and then the site is yours.
This track is for you if you want a site that looks established, at a fixed price, with no ongoing developer cost, and you are willing to spend one live training session learning to run it. It is not for you if you need a custom web application - a client portal, a marketplace, a platform with logins and accounts. That is outside what we build, and we will say so rather than quote it.
Sunday night, and the new price list should be live before Monday: you type it. Content changes are yours, unlimited and free - a price, a photo, your availability, a new testimonial, an announcement. Edit the page yourself, or tell your AI agent, in plain language: "Add this client testimonial under the coaching section." The agent writes the change. End-to-end tests, accessibility checks and an AI review verify it. If the checks pass, it publishes. You wait for no one and you pay nothing.
You do not need to know what a repository, a terminal or a DNS record is. You describe what you want the way you would describe it to an assistant. A change that fails the checks cannot reach your live site, and rollback to the previous version is always available. The written playbook and the live training session cover exactly this: editing, asking for changes, publishing, rolling back. If you can write a clear email, you can run this site.
Design and layout changes work the same way. "Move the booking section above the testimonials" is a complete work order: the agent prepares it, the checks verify it, it publishes. DevPowers does not review or approve your routine releases.
When the practice grows, the site grows by prompt: a new service page, a workshop signup, a lead magnet. You own the code, so none of it creates a new dependency. Larger features, integrations and redesigns are bought as change credits or quoted as a project - in writing, before work starts.
You can do it yourself - or hand it to us. Both stay open, permanently.
When a change is bigger than a prompt, or the hour is better spent on your own work, hand it to us by email or chat, the same way you reached us during the build. The work is bought as change credits: you receive an estimate in credits before anything starts, and you accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
Every change is estimated in credits, and you accept or decline the estimate before work starts. Credit pack prices are being set with the first clients and published once they are measured, not guessed.
Handover is the point of the whole exercise: the site is finished, and the powers to continue are yours. At handover you receive:
A handover should leave you more capable, not more dependent.
Yes. Content changes are yours, unlimited and free: a price, your photo, your availability, a new testimonial, an announcement. Edit the page yourself, or tell your AI agent in plain language - "Add this client testimonial under the coaching section" is a complete instruction. The agent writes the change, the automated checks verify it, and if they pass it goes live. No DevPowers involvement, no invoice, no ticket.
No. Doing it yourself is the default after handover - it is not a duty. Any change you would rather not make yourself, from a small edit to a new feature, you can hand to DevPowers by email or chat: the option stays open, it is simply not the default. The work is bought as change credits, and you receive an estimate in credits before any work starts; you accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
A change credit is a unit of paid work you buy in advance and spend whenever DevPowers does work on your site. You buy a credit pack; packs cost less as a short subscription than bought one-off. Each change consumes credits by its complexity, not by the time it takes. Credits carry an expiry date and unused credits expire after two months. Credits cover new work and repairs of damage you caused yourself. Failures caused by DevPowers are repaired free of charge and consume no credits. Credit pack prices are being set with the first clients and published once they are measured.
No. You will never open the code if you do not want to. You describe what you want in plain language, your AI agent writes it, and the pipeline checks every change before anything goes live. The written playbook and the live training session cover exactly this. If you can write a clear email, you can run this site.
We embed your scheduling tool - Cal.com, Calendly or the one you already use - into the page design, so clients can book a slot while they are reading about you, and the appointment lands in your calendar. Name your tool in the brief and it goes into the written scope.
There is no mandatory monthly payment to DevPowers. Hosting for simple, low-traffic sites is included for the first 12 months; CMS and shop projects have a small monthly fee stated in the scope. Hosting terms are renegotiated after 12 months. Your domain remains yours. Your AI subscription is paid directly to the provider you choose, at that provider's price. Change credits for larger work are bought only when you need them, and unused credits expire after two months.
Your domain registration always stays yours. DNS, alongside hosting, CI/CD configuration and secrets, is managed by DevPowers and is not client-modifiable - you will never be asked to edit a DNS record.
The first draft arrives within 5 working days after the deposit and your content or written content plan are received. No other turnaround time is guaranteed.
A change that fails the automated gates cannot reach your live site, and rollback to the previous deployment is always available - most accidents stop before they happen. If you override a stop-and-warn and the site is damaged, DevPowers repairs it and the repair is paid in credits: you receive an estimate first and accept or decline it. Failures caused by DevPowers are repaired free of charge and consume no credits.
Then we do it. Doing it yourself is the default because it is cheaper and faster for you, not because we stop working with you at handover. Send the change by email or chat, you receive an estimate in credits, and you accept or decline before anything starts. Nothing about the handover closes that door.
Larger work - new features, new integrations, a redesign - is bought as change credits or quoted as a project, in writing, before work starts. Credit packs cost less as a short subscription than bought one-off. And quite a lot of what feels bigger turns out to be a prompt once your agent is configured.
Then you leave, with everything. You own the source code, and your domain registration stays yours. The site runs on an open, standard stack, so any competent developer can take it over. There is no licence fee, no proprietary platform and no exit fee.
Tell us what the site needs to do. We acknowledge your email instantly and answer within one business hour - no call, form or booking calendar.