How a project runs at Aktify
An Authority project runs from a first call to a live site in four to six weeks. The approvals set the pace, we build once, and after launch the monthly plan takes over.
This is the flow behind every site we build, written for the Authority shape because it is the one we recommend for most businesses. Presence follows the same steps with fewer pages. Debut compresses them into five working days. Ecosystem is scoped on the call.
Before week one: the call and the proposal
The first call is on Google Meet. We ask what the site has to do, who has to act on it and where revenue is leaking today. You hear back inside 24 hours, and if it fits, the proposal that follows states the shape, the scope, the launch date and the payment terms. The team is planned around that date.
You sign, and the first invoice goes out: half of the project. We track your project’s scope, timeline, decisions and open items in our own studio system, updated as the work happens. Every approval is recorded there. WhatsApp is for anything urgent. You get a written update every week.
What we need from you before week one:
- Access, never a password: add contact@aktifystudio.com as a user at your domain registrar if you already have a domain (or tell us who manages it), your analytics and any tool we connect.
- Brand material: logo files, photos, anything already in print.
- The content you have, in whatever state it is in.
- One person who can say yes.
Week 1: strategy and blueprint
We audit what is leaking revenue, interview your buyers and map the ecosystem before a single pixel moves. Out of that comes one core message, one buyer, one action per page, and the page architecture. Your part is the interviews and honest answers. The blueprint is a written document; nothing is drawn yet.
Weeks 1 to 2: design
The conversion wireframes come first. They show every section, in order, with the argument it makes and the action it asks for. No colour, no imagery. The copy is written page by page at the same time, so the words and the layout arrive together. You review them with us on Google Meet and approve them by email. Moving a section is cheap here and expensive after the build, so we ask you to read them slowly.
Then the high-fidelity design in Figma, mobile-first, built on the approved wireframes: type, colour, spacing, imagery, motion. That, too, is reviewed on a call and approved by email. What you see is what gets built.
Weeks 2 to 4: build
The site is built in code, Next.js, in a repository that is yours once the project is paid. The CMS is wired so your team can run it. The module you choose is built into the site: online booking today, and chat, WhatsApp or reviews once they launch. The motion is tuned, and the speed is measured with Lighthouse on desktop and on a throttled phone before the site goes live. Your part in these weeks: send the final text and images, and check the preview link on your phone.
Launch, and what follows
- You sign off the preview.
- The second invoice goes out: the other half. It is paid before the site goes live.
- We point the DNS. A domain you already have stays at your registrar, in your name; if you had none, we registered one for you, and its renewal is part of your plan.
- The site is live. Your portal, with your numbers and your requests, is coming soon.
- Grow starts, included for three months.
Four to six weeks is a range because the approvals are the clock.
“We contacted Aktify Studio to build our website and are extremely satisfied. From start to finish, communication was clear and pleasant. Highly recommended! Excellent service!”
After launch: the monthly plan
The plan replaces maintenance. Hosting, security, backups and uptime are ours to run. Changes come in two sizes; once the portal launches, you ask for them there.
| Request | What it is | Live in |
|---|---|---|
| Small | Under an hour, no design change: text, images, prices, hours, a team member, a FAQ. | 48 hours |
| Large | Under a day, may change layout: a new page or section, a landing page, a redesigned block, a module reconfigured. | Five working days |
| Not a request | A new module, a rebrand, a new integration. Quoted as a mini-project, never absorbed into the plan. | Quoted |
Unused requests do not roll over. After the three included months, the plan you chose at launch carries on, with a reminder a week before. Month to month, no lock-in.
What you own at the end
- The code, in a Git repository with its full history, handed over whenever you ask.
- The domain: the one you had, or the one we registered for you, transferred whenever you ask.
- The content, in a CMS with an export.
- The accounts (analytics, booking, mail) in your name.
- The design source, when identity was part of the project: logo, palette, type, style guide.
Nothing on that list needs us in order to keep existing.
The same flow, in five working days
Debut is the flow with the fat cut out. One page, up to six sections, your content polished by us. There is one revision round: you see the finished page, you ask for your changes, it goes live. It is paid in full up front, and it includes three months of Host: hosting, security and backups, with changes quoted per request. Anything past that scope is a Presence project, and the flow above applies.