Questions, answered properly

We cover six disciplines under one roof: digital marketing, creative production, website engineering, Web3 and blockchain, AI and automation, and business consulting. Most engagements draw on more than one — a launch usually needs creative, media and a site that can take the traffic.

Startups, established businesses, creators and blockchain projects. The common thread is a specific outcome someone is accountable for, rather than a general wish to 'do more marketing'.

Per engagement, after we understand the scope. We do not publish rate cards because the same brief can mean very different amounts of work depending on what already exists, what needs rebuilding and how fast it has to move. You get a written scope and cost before anything starts.

Both. Project work suits a defined deliverable such as a site build or a launch campaign. A retainer suits ongoing work such as paid media management or content production, where the value comes from iterating every week rather than shipping once.

Yes, and often that is the sensible route. A contained first piece of work tells you how we operate and tells us how your business actually runs, which makes the scope of anything larger far more accurate.

The people doing the work. You will not be handed from a pitch team to an execution team you have never met, and you will have a direct line for questions between scheduled updates.

Access to whatever already exists — analytics, ad accounts, the current site, brand assets — plus one person on your side who can make decisions. The second one matters more than people expect; work usually slows down waiting for approvals, not for production.

Yes. Deliverables, source files, code and accounts are yours, and we hand over access rather than holding it. Anything built on your accounts stays on your accounts.

Paid search and paid social, organic social, SEO, content and email. Which of them we recommend depends on where your buyers already are and what your margins can support, not on which channel is fashionable this quarter.

By looking at what already works and where the drop-off is. If traffic is healthy but conversion is not, spending more on traffic makes the problem more expensive rather than smaller. The first pass is usually diagnosis, not spend.

It depends on the channel, and anyone who gives you a date without seeing your account is guessing. Paid media produces usable signal quickly because you control the volume; SEO and content compound over months. We will tell you which one your goal actually needs before you commit budget.

Against the business outcome you care about — qualified leads, revenue, cost per acquisition — with the channel metrics underneath it as supporting detail. Impressions and reach are diagnostic, not results, and we do not lead a report with them.

Yes, and we ask you to grant access to accounts you own rather than creating them under ours. It is slightly more setup at the start and it means your history, audiences and spend data stay with you if we ever stop working together.

Regularly. Sometimes we own a channel outright, sometimes we handle strategy and review while your team executes. Both work as long as it is clear which one it is.

No, and we would treat a guarantee from anyone else as a warning sign. Search rankings and auction costs are set by competitors and platforms we do not control. What we commit to is method, measurement and honest reporting on what the numbers are doing.

Modern React frameworks such as Next.js for anything custom, and established platforms where a CMS or storefront is the better fit. The choice follows who needs to edit the site afterwards and how it needs to scale.

If that is a requirement, say so at the start — it changes the build. We can wire a CMS so your team edits pages without touching code. Where a site is largely static, hard-coding content is faster and cheaper to run, so it is worth deciding deliberately rather than by default.

It is a build constraint, not a phase at the end. Server rendering, image optimisation, restrained client-side JavaScript and measured Core Web Vitals. Retrofitting speed into a finished site is far more expensive than building for it.

Yes. Semantic markup, keyboard operability, focus management, colour contrast that meets WCAG AA, and screen-reader testing of interactive components. It is also a legal exposure in a growing number of markets, so it is not treated as optional polish.

Yes, and this is the part rebuilds most often get wrong. It means mapping every existing URL, redirecting the ones that change, preserving metadata and structured data, and watching Search Console closely after launch rather than declaring victory on launch day.

You get the code, the accounts and documentation for how it is deployed. Ongoing support and iteration can be arranged, but the handover is complete either way — you are never dependent on us to keep the site running.

Yes. We can work from your existing brand and design system, or design the interface as part of the engagement. If you already have a designer, we are comfortable building to their files.

Go-to-market and communication: positioning, launch strategy, community building and growth for onchain projects. We are the marketing and strategy side of a launch, working alongside your protocol engineers.

No. Contract development and security auditing are specialist disciplines where being approximately right is worthless, and we will point you at dedicated auditors rather than take that work on. Anything that touches user funds should be reviewed by people who do only that.

By giving people a reason to be there beyond price speculation. Moderation, communication rhythm, genuine answers to hard questions, and a clear explanation of what the project does. Communities assembled purely with incentives leave the moment the incentives stop.

On the communication side — narrative, documentation, community readiness and launch sequencing. Token structure, legal classification and jurisdiction are questions for your lawyers, and they should be settled before marketing starts rather than after.

No. It inflates the metrics you use to make decisions, it is visible to anyone who checks properly, and it does lasting damage to a project's credibility when it comes out. If a proposal depends on fake numbers, it is not a proposal we will make.

Yes, and that is usually the most useful point to start. Positioning and documentation decided before launch are much cheaper to get right than a narrative corrected after the market has already formed a view.

The repetitive, rule-shaped work between systems: lead routing and qualification, CRM updates, reporting, content repurposing, support triage and internal handoffs. Good candidates are tasks done often, the same way each time, by someone who resents doing them.

That is not what we optimise for, and it is usually the wrong target. The work worth automating is the administrative overhead sitting on top of skilled roles — the copying between tools, not the judgement. The gain is capacity, not headcount reduction.

We scope what data an automation genuinely needs and keep it to that. Where a workflow touches personal or commercially sensitive data, the storage location, retention and access rules are agreed in writing before anything is built, not decided afterwards.

Assume it sometimes will, and design for it. Anything customer-facing or irreversible gets a human review step; automation runs unattended only where a mistake is cheap and detectable. A workflow with no failure path is not finished.

Usually. Most business tools expose an API or webhook, and we prefer connecting what you have over migrating you onto something new. If a tool genuinely cannot integrate, we will say so rather than build a fragile workaround around it.

Your call. They are documented and handed over so your team can run them, and we can stay on for maintenance if you would rather. Either way you get the documentation — an automation nobody understands is a liability the first time it breaks.

Understanding how the business currently makes money, where growth is actually constrained, and what to change first. It usually starts with a diagnostic phase, because the stated problem and the real one are frequently not the same thing.

No. A deck nobody executes is an expensive way to confirm what a team already suspected. Recommendations come with a sequence, an owner and a way to tell whether they worked — and we can execute the parts that fall inside our other disciplines.

Yes. The questions are different — positioning, pricing, which channel to prove first, what to build in-house versus buy — but the discipline of deciding deliberately rather than by default matters more at that stage, not less.

Meaningfully. Consulting done at arm's length produces recommendations that ignore how the business actually operates. Expect interviews with the people doing the work and regular sessions with whoever can act on the conclusions.

Then that is what we will tell you, including when it means less work for us. A recommendation you cannot trust to be against our own interest is not worth commissioning.