Questions, answered.

We are a creative technology studio for advertising agencies. We build physical and digital products, campaign technology, automations, and creative generation pipelines. We also build the tools and systems that help the agency run.

Your agency leads the client relationship. We can build under your agency brand and agree the technical responsibilities with your team.

Yes. The work can be physical or digital, depending on the brief. Tell us what you want to make, who it is for, and when you need it. We will help define the build and the scope.

Send a short brief. We reply within 24 hours, discuss the work, then agree the scope, price and start date before work begins.

Bring the idea, the people using it and any deadline or dependencies you know. A technical specification is not required to start the conversation.

Builds are priced against an agreed scope. The first conversation identifies what needs investigating before we can quote the work.

We agree the start date after reviewing the scope and current commitments. Include your deadline in the brief so we can discuss feasibility early.

Forge software builds include hardening and documentation in the final phase. Handover responsibilities and any post-launch support are agreed for the build. Physical products follow their own testing and production plan.

Forge builds physical products, software and production pipelines. Standard software engagements use an agreed twelve-week scope; hardware is scoped per build. Masthead builds websites and campaign experiences. Orbit combines a reduced fee with an agreed stake.

The price is fixed, so a build running long is our problem to solve, not your invoice to absorb. That's the point of the structure, and why we scope tightly before we sign.

Forge builds and Orbit partnerships have an agreed scope. Masthead Evolve defines website improvements per quarter. Fractional CTO work is a separate ongoing advisory arrangement.

An agency pricing assistant that works with your rate cards and previous proposals. Describe a scope to draft quotations and proposals, then review the result before using it.

Pulse is in development. It uses AI personas to explore how different audiences could interpret a campaign and surface potential misreadings, cultural friction and backlash risks before publishing. These simulated perspectives support human review; they are not audience research or a prediction of real reactions.

Beacon combines Crawl-Sim’s bot-access checks with a separate Ora agent-readiness assessment. Findings help identify technical barriers and unclear content. They do not predict citations or rankings. The audit page explains what is checked and shared before you scan.

It's making your company legible and quotable to AI answer engines like ChatGPT, Claude, and Perplexity, so you appear in the answer they give a user directly, not only in a list of search results.

No. Classic search ranking and AI-answer surfaces read different signals. You can rank first and still be absent from the answer a model writes.

Crawlability, almost always. If a non-rendering bot fetches your page and gets an empty shell, the model has nothing to read. Server-render your real content and clear your robots.txt and llms.txt directives first.

Hosting, processing providers, regions, access and retention depend on the build. Agree those requirements in the scope before connecting data or systems. Ask for an NDA before sharing confidential material.

Bring your data protection and procurement requirements into the first conversation. Request the relevant processing terms, provider information and access plan, then agree responsibilities for the proposed build. The security page explains the decisions to discuss.