Skip to content
Viewership Inquire

Custom AI builds, scoped to your problem.

Not every problem fits a category. Tell us what your team spends too much time on, and we will come back with a written outline and a fixed quote for a system built around it.

Request an introduction How it works

What a build can be

  • Internal agents

    An assistant that drafts proposals from your past wins, answers sales questions from your docs, or preps briefs before meetings.

  • Workflow automation

    Work that moves between your CRM, inbox, Slack and docs, done automatically with a person approving the steps that matter.

  • Research and monitoring

    Competitor pricing, reviews, job posts or mentions, checked on a schedule and summarised for the people who need it.

  • Data connections

    MCP servers and integrations that give Claude secure access to your own data, so your team can ask questions of it directly.

  • Prototypes

    A working version of an idea in weeks, so you can test it with real users before committing to a full build.

What we ask on the first call.

  1. The problem

    01

    What takes too long, costs too much, or never gets done.

  2. Who does it today

    02

    The people and steps involved, and where the work slows down.

  3. The tools involved

    03

    The systems the work touches, and whether they have APIs we can use.

  4. What done looks like

    04

    How you will know the build worked: time saved, output, revenue.

  5. Constraints

    05

    Security, compliance, budget and the date it needs to be live.

  6. Who signs off

    06

    Who approves the scope, and who will use the result every day.

How a quote comes together

  1. Introduction. A 30-minute call with a founder. You describe the problem; we ask a lot of questions.
  2. Outline. A short written document: what we would build, how it would work, what it needs from your team, and what we would leave out.
  3. Quote. A fixed price for the build and a timeline, plus an optional retainer if the system needs tuning after launch.
  4. Build. We work in short cycles and show progress as we go, so there are no surprises at the end.
  5. Handover. Documentation, training, and the code and prompts transferred to you.

Start with the problem, not the tool.

Most AI projects stall because they start with a tool looking for a use. We start with the work: who does it, how often, and what it costs when it goes wrong. If the answer is a content system or a reporting system, we will say so. If it is something new, we will scope it from scratch.

And if a better prompt or an off-the-shelf product would solve it, we will tell you that too.

Questions, answered.

01

How do you price a custom build?

After the first call we send a written outline of what we would build and a fixed quote for it. If the system needs ongoing tuning after launch, we quote that separately as an optional retainer.

02

What if our needs change partway through?

We agree the scope up front so the price holds. If something new comes up, we write it down, quote it, and you decide whether to add it now or later.

03

Do you only build with Claude?

Most of our builds use Claude, but we choose the model and tools that fit the job, and can work inside your existing cloud accounts if your security team requires it.

04

Do we own what you build?

Yes. Code, prompts and workflows are yours at handover, with documentation so your team or another developer can maintain them.

05

Is any project too small?

If a well-written prompt or an off-the-shelf tool would solve it, we will tell you on the call and point you to it instead of quoting a build.

Built for one brand. Yours.

Every engagement starts with a 30-minute call with a founder. You get a straight answer on fit, scope and price before anything is signed.

Request an introduction