For agencies with a development team or delivery partner
Your next client website.
A reusable starting point.
Build local-business websites from one Next.js engine, with booking, quote-request and admin workflows already in place. Your team configures each client site and delivers it under your agency’s brand.
Built for agencies serving different markets. Language, currency and local business content can be configured for each client.
- Agency licensing · scope agreed together
- Non-exclusive licence
- First month of support included in the proposed offer
Barber · Studio
One codebase, configured per client
Choose a preset, a presentation style and a site feature tier. These examples show what changes between client configurations—and the workflows your team starts with.
Demonstration business
Harbour & Co. Barbers
Barber preset · “Studio” presentation · Full package
What this shows
- A six-step appointment flow: service, barber, date, time, details, review.
- Services, prices, staff and opening hours all come from the client's configuration.
- Booking can also hand off to WhatsApp, phone or an external booking link, depending on the package tier.
Fictional business and contact details. Sample prices are shown in pounds.
Demonstration business
Brightline Build
Construction preset · “Vantage” presentation · Full package
What this shows
- A quote-request workflow instead of appointments: service, property, address, details, review.
- Currency and service catalogue set by configuration (shown here in pounds).
- Longer quote workflows can add project type, size, budget, timeline and photo steps. Photo uploads need storage to be configured.
Fictional name and placeholder details. Prices are preset sample data.
Demonstration business
Freshfold Cleaning
Cleaning preset · “Meridian” presentation · Booking package
What this shows
- A third presentation style, applied to a different trade.
- Responsive layouts are included. Your team still checks each client’s content and workflows on the devices they use.
- Sites can be multilingual, including right-to-left languages, when a client needs it.
Fictional name and placeholder details. Copy and photography come from the preset's samples.
Demonstration data
Staff admin
Quote requests for Brightline Build
What this shows
- Submitted requests with search, status filters and a details panel showing contact and consent records.
- Booking clients get an appointments view with filters, rescheduling, cancellation and notes.
- Admin access supports a shared password or configured Supabase user accounts. Staff permissions are not separated into roles.
Requests were submitted through the engine's own form API on a local build, which uses a temporary in-memory store. Live sites need a configured database.
Follow the illustrated product tour before a call. These are local demonstrations; public interactive demos are not available yet.
Configure, deploy, then operate
The engine handles the repeated parts. Your developers handle configuration, deployment and anything that's specific to the client.
-
Choose a business preset
Start from one of seven presets. Each one provides default copy, page structure and the right workflow for that trade.
- Barber
- Salon
- Beauty
- Restaurant
- Cleaning
- Construction
- Plumbing
-
Configure the client
Each client is a configuration folder covering identity, branding, services, staff and theme. Choose from three presentation styles and three site feature tiers: landing, booking or full. These are website capabilities, not agency licence plans.
Tools scaffold and validate client configurations. A separate intake form and generator support structured preset content.
-
Deploy and operate
Each client needs its own deployment. Configure Supabase for persistent data and Resend for email, then test the complete workflow on your chosen host.
To change content, you edit the configuration and redeploy. There's no live visual editor for clients.
What the engine provides
- Marketing pages, booking and quote-request workflows
- Staff admin for appointments and quote requests
- Transactional email templates (with Resend configured)
- A versioned database schema, plus a local demo mode that needs no setup
- Deployment, handover and maintenance checklists
What your agency is responsible for
- A developer comfortable with Next.js, React and TypeScript
- Client content, photography and approvals
- Hosting, domain, database and email accounts for each client
- Deploying, testing and maintaining each client site
- Any custom features beyond the supported workflows
Software, setup and support together
The proposed agency offer combines source access, a first-client setup and technical handover. Distribution preparation is still in progress; delivery is agreed only after the release is ready.
-
Licensed software
Non-exclusive commercial use of a prepared source package. The distributable must pass its release checks before handover.
-
Documentation
Setup, architecture, deployment and maintenance guides for your developers.
-
Guided onboarding
A guided first-client setup using supported features, with deliverables agreed in the proposal.
-
First month of support
10 hours of email-based setup and troubleshooting during the first month from technical handover. The target initial response is within two working days; resolution time depends on the issue.
-
Optional paid support
After the first month, further support or development is available as paid work, on terms agreed separately.
Who it suits, and who it doesn't
A good fit if you…
- Build websites for local businesses regularly, not occasionally
- Keep getting similar booking, enquiry or quote requirements
- Have an in-house developer or reliable delivery partner who can maintain a Next.js codebase
- Are happy to deploy and look after each client site yourselves
- Want to brand finished sites as your agency's own work
Probably needs more work, or something else, if…
- Clients edit their own pages. There's no visual CMS, so a site builder or headless CMS may suit you better.
- You need online payments or a shop. These aren't part of the engine.
- You want two-way sync with an existing booking system. The engine can link out to one but doesn't sync with it.
- You want one platform hosting many clients. Each client is a separate deployment.
- Your team doesn't write code. This engine is run by developers, not a no-code tool.
An agency licence that matches your delivery model
Agency licence proposal
Let’s scope your agency’s use.
Tell me how many client sites you expect to deliver and who will maintain them. We’ll discuss budget and fit, then agree a written proposal before any purchase.
- Annual, non-exclusive commercial licence for your agency
- Source delivery and documentation, subject to release readiness
- Guided onboarding and first-client setup
- 10 hours of support in the first month
Not included: hosting, domains, database and email services (billed by those providers), custom development, and support after the first month.
What your proposal will settle
- The engine
- Mukarram Ali retains ownership of the reusable engine. Your agency receives non-exclusive commercial usage rights.
- Your client websites
- The intended use is building and selling finished client websites under your agency’s brand. Licences run annually, with the site allowance and renewal price set out in your proposal. If you do not renew, existing licensed client websites may keep running and be maintained. New client sites and access to new releases require renewal.
- Not the engine itself
- Standalone resale of the engine is excluded. The agreement must separately define what a client or replacement maintainer receives to run a finished website.
- Agreed in writing
- Site allowance, renewal price and process, client handover, updates and security fixes, delivery date, final price and applicable tax treatment. These details are agreed in your proposal.
Questions agencies ask
Is this only for UK businesses?
No. The UK-style demos are fictional examples, not a market restriction. Agencies can adapt language, currency, contact details and local content for markets such as the US, UK and Canada. Regional formatting, integrations and legal requirements should be checked for each project; support for every country is not implied.
What does an agency licence cost?
Pricing is discussed after we understand your intended client-site allowance, setup needs and support requirements. We’ll cover budget early, then put the price and terms in a written proposal. There is no fixed public package price yet.
Do we get the source code?
Source access is part of the proposed offer. The agency distribution is still being prepared and must exclude other clients’ material, credentials and private development history before delivery.
Who owns what?
I keep ownership of the reusable engine. Your agency gets non-exclusive commercial usage rights as written in the licence. The content, branding and client relationships you create stay yours.
What do our clients get at handover?
The proposal must state how clients and replacement maintainers can run, host and modify finished sites, while preventing standalone resale of the engine. Those handover rights are still being defined; do not promise them to a client before they are agreed.
How is a client site deployed?
Each client has a separate deployment and backend configuration. Your team supplies hosting, a database and email services, and follows the deployment and maintenance checklists.
What are the ongoing costs?
Hosting, domains, database and email are separate from the licence. They are paid separately to the providers. Your team should check current commercial-use terms and prices before quoting a client.
How do clients change their content?
Content is held in configuration. To change it, your team edits the client's configuration and redeploys. There's no live visual CMS, so content updates are usually done by your agency as a service.
Can we customise it?
Yes, within the licence terms. Without writing new code, you can configure branding, themes, presentation style, services, staff, package tier and languages. Anything beyond the supported workflows is development work, either by your team or as separately agreed paid work.
What support is included?
The first month from technical handover includes 10 hours of email-based setup and troubleshooting, with a target initial response within two working days. Custom development is quoted separately. Working days, time zone and detailed scope are set out in the proposal. Support after the first month is paid separately.
What happens if we don’t renew?
Existing licensed client websites may keep running and be maintained. Without renewal, you cannot create new client sites under the licence or obtain new releases. Ongoing hosting and maintenance remain your agency’s responsibility.
Do we get future updates?
The proposal must specify the supplied version, update eligibility, security-fix arrangements and how your team applies changes. These terms are still being defined; lifetime updates are not promised.
Are other agencies already using it?
Not yet. Agency licensing is new. The walkthrough is there so you can judge whether the engine fits your upcoming projects before you commit to anything.
See the engine against your next client brief
Speak with Mukarram Ali, the developer behind the engine. Bring a typical client brief; we’ll cover:
- Setting up a client from a preset, live
- The booking, quote-request and admin workflows
- What deployment, data and email setup involve
- Licence scope, client handover and support
- Whether it fits the projects you have coming in
Mukarram Ali
Engine developer · Your contact for the walkthrough and technical handover
No payment is taken here. Prefer email? Write directly using the address above.