The questions we're asked,
answered honestly.

We run marketing, development, design and AI as one senior team. Agencies use us as a white-label delivery partner under their own brand, and we work directly as a digital growth partner for brands. Founded 2004: 2,500+ projects, 30+ countries, first deliverable inside 14 days of a signed NDA.

From a standing start: a written proposal within 48 hours of your enquiry, and the first deliverable within 14 days of the NDA being signed. Agencies already on the partner bench move faster still, because the rate card and NDA are done before a brief exists. What we won't do is start before the NDA. That ordering protects you, not us.

No. A URL and a sentence about what's bothering you is enough for the website review. A rough goal is enough to start scoping: turning vague intent into an itemised plan is part of the job, not a prerequisite for it. The proposal you get back effectively becomes the brief: deliverables, team, timeline and price, all challengeable line by line.

A senior strategist records five minutes on your website: where it is slow, where search rankings leak, how visible you are to AI assistants, and where conversions fall through. It arrives within 48 hours, it is yours to keep, and it needs nothing from you but a URL. No budget, no brief, no retainer. If we think we can help, we say how; if we can't, we say that instead.

Within 48 hrs of your message landing, the same window we quote for proposals, and the one we track ourselves against. Most enquiries hear back sooner. If yours needs digging before we can answer properly, you get a note saying exactly that rather than silence.

Yes, as standard and before any detail changes hands, ours or yours, whichever your legal team prefers. For white-label work it is the first document on file. From signed NDA to first deliverable averages 14 days.

Because scopes vary too wildly for a fixed menu to mean anything: a five-page brochure site and a headless replatform are both "web development", at very different points on the range. What we do publish, on the pricing page, is an indicative INR/USD range for each engagement shape. That way you can see the realistic band before you talk to anyone. The trade for the real number: one short call, then an itemised proposal within 48 hrs listing deliverables, team, timeline and price. That lets you challenge every line you would be paying for.

Three. Projects: fixed scope, fixed quote, for work with a clear finish line. Retainers: a monthly programme with an itemised deliverables list, for marketing work that compounds. Dedicated pods: a named senior team at a monthly rate, the shape most white-label agency partners and scaling brands use. Many clients move between shapes: a project first, then a retainer to grow what was built.

Yes, that's what the project shape is. Fixed scope, fixed quote, milestone dates in the proposal. If the scope changes mid-build, the change is re-quoted the same itemised way, so the price moves visibly with the work instead of arriving as a surprise invoice.

None to start: the first audit or website review is free, with no retainer required. Projects are quoted for their fixed scope. For retainers and pods, the commitment is agreed per proposal rather than a blanket lock-in; you'll see the term in writing before you sign anything.

Mostly speed and shape. Recruiting a senior team takes months of sourcing, interviewing and notice periods before anyone writes a line of code; a pod is scoped, interviewed and delivering within 14 days of the NDA. The shape flexes too. Roles change as the roadmap changes, under agreed notice, without redundancy processes. We won't invent a "save X% versus salaries" figure, because the real comparison depends entirely on your market and mix. The rate is itemised per role, so you can run that comparison yourself with real numbers on both sides.

Yours, for the day to day. The team joins your Slack or Teams, your Jira, Asana, Trello, ClickUp or Basecamp, and follows your process, including your reporting templates if you're an agency. Requests, approvals and the weekly review live in your Prism workspace, which you get a login to on day one, so there is one record of what was asked, decided and shipped.

A written weekly summary in your Prism workspace: what shipped, what moved, what's next, against the metrics named in the proposal, plus a monthly deep-dive connecting the work to sessions, pipeline or revenue. If a number went the wrong way, it's in the report with a reason and a plan, not smoothed out of it.

Yes: a large share of engagements run exactly that way. Our specialists work inside your standups, sharing your tracker with your developers or marketers. Kickoff defines who owns what so nothing falls between the teams. Documentation is kept shared from day one, so the knowledge stays with you rather than leaving when the engagement ends.

The pod's project manager runs delivery (standups, backlog hygiene, blockers, the weekly review in Prism) and you set direction and priorities. If you'd rather run the backlog yourself through your own product owner or producer, the pod slots into your process instead. Either way you're never the one chasing individual contributors; that's what the PM is for.

You'll hear it from us before you have to raise it: flagging problems early is in the reporting cadence on purpose. First we fix: a written plan with dates. If the engagement genuinely can't deliver what it promised, we say so and wind down under the notice terms you agreed at the start. Everything is handed over cleanly: code, designs, accounts, documentation. No dead retainer months, and no hostage-taking on the way out.

We tell you straight away, propose a replacement for you to interview, and overlap the handover wherever notice allows. Account knowledge is kept in shared documentation from day one precisely so it never lives in one head. Continuity is the product here. It's a large part of why the average partner keeps their team past two years.

White-label means we deliver under your brand. You own the client relationship, set the retail price and keep the margin, and we invoice you at the wholesale rate card. A referral means handing the client to us for a fee. You earn once and lose the recurring revenue. Nearly all partners choose white-label, and the zero-competition clause applies either way: your clients are never approached by us, full stop.

Not from us. Invisibility is how the work is delivered, not a courtesy we extend. Reporting ships in your templates, the NDA covers the relationship itself, and when we join client calls we join as your team, on your email addresses and in your tools if you prefer. Our name appears nowhere on the work, and the contract says so. In 21 years, no partner's client has ever heard it from us.

No, and it's in the contract, not just a promise. Every partnership includes a zero-competition clause: we never approach, pitch or accept your clients directly. A 12-month blackout applies after any engagement ends. If one of your clients ever comes to us directly, we tell you and decline the work. Client calls happen under your brand, with your team leading. We join as your people when you want us there.

You buy at the wholesale rate card, agreed once, in writing, the day you join, and sell at whatever your market supports. We never publish your retail pricing, never contact your clients, and never squeeze the rate mid-project. Proposals against the rate card arrive within 48 hours, itemised by deliverable so you can drop them straight into your own scope documents.

All of them: SEO and AI-search work, PPC, content and email, Shopify, WordPress and headless web builds, web and UI/UX design, and AI builds like chatbots and workflow automation. Most partners start by reselling the discipline they lack in-house, typically development or SEO, then widen once the first project lands. One rate card covers every service.

Yes, that's the normal path. Most partners vet us months before they have work. Joining the bench gets you a rate card, capability pack, NDA and a named contact, so the day a client signs, delivery starts immediately.

Joining the bench costs nothing and commits you to nothing: it's an NDA plus a rate card on file. Delivery work runs on per-project statements of work or a monthly retainer, whichever fits the engagement. If you leave, everything we built transfers with a proper handover, and the zero-competition clause keeps protecting you after the last engagement ends. Ask for the clause text before you sign.

Quick technical wins land in the first weeks. Meaningful ranking and traffic movement usually shows over the months that follow, compounding after that. Competitive markets take longer; we set that expectation honestly, per keyword group, before any contract is signed. The earliest signal is in Search Console: impressions on the keyword groups we targeted move before clicks do, so the weekly report tracks impressions per group first. If a group's impressions do not move across the following reports, the plan for that group changes and the report says why.

No. Rankings are Google's decision, not ours, and not any agency's. Our contract binds the work instead: audits delivered, fixes shipped, content published, links earned, reported weekly. Judge us on the published case above, written up in full rather than averaged.

Answer Engine Optimization and Generative Engine Optimization make your content citable by ChatGPT, Perplexity and Google AI Overviews: structured data, answer-first architecture, entity clarity. We build both into every engagement alongside classic SEO.

No, though they share foundations. SEO earns positions on a results page, and its success event is the click. AEO earns the mention inside the written answer that ChatGPT, Perplexity or an AI Overview produces, where there may be no ranking and no click at all. The craft overlaps (a crawlable site, structured data, real authority help both), but AEO adds work classic SEO rarely prioritises: answer-first formatting, entity consistency and AI-crawler access. The two are strongest run together, which is why our SEO retainers include the answer layer. This page exists for teams who need it standalone.

No, and we'd encourage you to walk away from anyone who says yes. Which sources an assistant cites is decided inside systems nobody outside OpenAI, Anthropic, Perplexity or Google controls. The same question can produce different answers for different users, sessions and model versions. What we commit to contractually is the work that makes citation possible: schema deployed and validated, entity consistency established, answer-first pages shipped, crawler access verified, all reported weekly. That is the honest version of this service, and the only version worth paying for.

In two columns, because citation tracking is a young discipline, and pretending otherwise would mean selling you a dashboard of guesses. What we can measure: AI referral sessions arriving in your analytics, AI Overview appearances on the queries we track, scheduled spot-checks of the major assistants recorded over time, and every piece of input work: schema validity, crawler access, answer-first coverage. What nobody can measure yet: the assistants publish no impression or citation logs, and answers vary between users. Every report separates those two lists explicitly, so you always know which claims rest on data.

You do, fully and from the start. IP assignment is written into the contract, and the repository is created in your own accounts on day one. Documentation and credentials are handed over as we go rather than ransomed at the end. If you leave, you take everything: code, infrastructure, runbooks. No licence-back clauses, no proprietary frameworks you can't maintain without us.

Our software development services cover the stacks most businesses actually run: JavaScript and TypeScript (React, Next.js, Node.js), PHP (WordPress, WooCommerce, Laravel), Shopify and headless commerce (a custom front end on a commerce engine), plus the API, cloud and release-pipeline work around them. We staff engineers who ship in your stack every week. If we don't have genuine senior depth in a technology, we say so and point you elsewhere rather than learn it on your budget.

QA is built into every sprint, not bolted on at the end. Automated checks run in CI on every merge, and a QA engineer does manual passes across browsers and devices before each demo. Defects are logged, fixed and retested before you review the build. If you only need testing, our QA & Testing service runs the same process against code written by anyone.

Yes, and it's common enough that we run a dedicated Fix & Rescue practice. We audit what exists first (code, campaigns, or both) and tell you honestly what's salvageable before quoting the recovery, so you're never paying twice for the same work without knowing why.

Yes, post-launch work runs as one of the same engagement shapes as everything else: a retainer for ongoing improvements, maintenance and monitoring, or a dedicated pod when the roadmap justifies a standing team. Handover is complete either way, including code, credentials and documentation, so continuing with us is a choice you re-make on merit, not something the architecture forces on you.