What this will actually be like.

What happens when you get in touch

Your message goes to one inbox and a real person reads it. You get a reply within one business day — not an auto-responder, and not a calendar link before anyone has understood what you need.

That first reply is usually questions: what the business does, how people find you today, what is actually going wrong. If it is clear enough already, it is a straight answer instead.

You are talking to the person who will be accountable for the work. Nobody hands you on after the sales part is over, because there is no sales part.

How scope gets agreed

Before anything is built, you get it in writing: what is included, what is not, what it costs, and what we need from you.

The 'what is not' half matters as much as the rest. Most project disputes are not about quality — they are about two people holding different pictures of what was being bought. Writing the boundary down before starting is how that stops happening.

If the shape of the work changes as we go, that gets written down too, and agreed before it is built rather than appearing on an invoice.

How we talk during the build

You have one point of contact, and you can reach them by email or WhatsApp — whichever suits you.

You get updates as the work reaches points worth showing, not on a schedule that exists to look busy. If something is blocked or turning out harder than expected, you hear that early, from us, rather than discovering it at the end.

You never have to explain your business twice.

How feedback and revisions work

You see the work as it comes together, on a real link you can open on your own phone — not as screenshots.

How many rounds of revisions are included is written into the scope before we start, so nobody is guessing what is fair. Changing your mind about a colour is a revision. Adding a booking system is new scope, and gets quoted as such rather than absorbed silently and resented.

If something we built is wrong or broken, that is not a revision. That is us fixing our own work.

What happens at launch

It goes live, and you own it: the code and the content are yours, under the terms agreed at the start. Ask for the source at any point and you get it — during the build, at launch, or two years later.

By default it runs on our hosting and our accounts. That is a deliberate choice rather than an administrative one: when something breaks, it gets fixed directly, instead of waiting on a login or a permission that only you can grant.

If you would rather it ran on your own hosting, in your own accounts, say so and that is what we do — with everything handed over, source code included. The honest trade is that nothing can then be touched without you in the loop first, so a fix starts with a request for access rather than with the fix.

Third-party pieces — themes, plugins, fonts, stock photography — come with their own licences and are licensed to you rather than transferred. Which ones a project uses is listed before you approve it, never discovered afterwards.

You get shown how to change the things you will want to change: text, images, prices, opening hours, posts. The goal is that routine updates never require calling us.

Two things you agree to at the start rather than hear about at launch: the site carries a DEV AIO SOFT LLC credit line in its footer, and once you are live we may show the project as published work — named, linked and described — on our Work page. Anything you have not launched stays off our site until you go live.

What happens after

What we cover after launch is agreed per project and written into the scope with everything else — what is included, how to reach us, and what falls outside it.

We would rather write that down honestly for your project than publish a support promise here that we have not thought through for your situation. A vague commitment made to everyone is worth less than a specific one made to you.

If you want a maintenance arrangement, ask and we will tell you plainly whether it makes sense for what you have.