How we work / Alongside your team

Choose a first opportunity. Build from there.

We join your team, choose useful work, and build toward real operation. Working sessions, actual users, and regular reviews keep the next step tied to what your business needs.

Where to begin

Start where you are.

Find the opportunity

You see the potential. The first project is still unclear.

Begin with an AI opportunity assessment. We examine the evidence with you and choose work worth building.

The assessment
Improve a workflow

You know which work needs to get better.

Begin with a concrete build. We work with an internal owner, connect to your tools, and test with real users.

See a working example
Develop the team

Your people are ready to do more with AI.

Begin alongside them. Pairing and working sessions help engineers, product teams, and operators apply AI to the work they own.

See team adoption

These are starting situations within an embedded engagement. We help you choose the right mix as we learn together.

AI opportunity assessment

Find the first opportunity worth building.

We examine the work and the evidence behind it: customer conversations, documents, systems, and the experience of the people doing the job.

Together, we identify where AI can make a useful difference, what stands in the way, and which opportunity to tackle first. The scope follows the questions your business needs answered.

  • A shared picture of the problem, grounded in evidence
  • A prioritized set of opportunities and practical constraints
  • A concrete next step, with an internal owner and a way to judge progress

At Visiting Media, an assessment informed product and organizational priorities, then developed into ongoing customer intelligence built with the client’s own engineer.

Read the assessment story

The first cycles

Build the system and the capability together.

01

Understand

Learn the work from the people doing it.

Study the workflow, information, tools, and exceptions. Bring customer evidence and the team’s experience into the same picture.

  • Conversations with internal owners
  • Data and system mapping
  • Evidence and constraints
02

Choose

Agree on a useful first opportunity.

Choose work with a clear purpose, a person who will use it, and a way to judge whether it helps. Keep priorities visible in one shared queue.

  • A named internal owner
  • Examples of good results
  • Shared priorities and tradeoffs
03

Build + validate

Test against real work.

Connect the system to the tools and information it needs. Review its output with users, include appropriate human controls, and improve it through working releases.

  • Production engineering
  • Quality checks and review
  • Feedback from actual users
04

Grow capability

Help your team take on more.

Pair with internal owners throughout delivery. Document the operating path, share reusable tools, and help people learn to judge, run, and improve the system.

  • Pairing and working sessions
  • Documentation and reusable tools
  • Operating responsibility and handover

The engagement

One team. One shared set of priorities.

Choose a monthly level of investment. We direct that capacity toward the agreed work and adjust priorities as you learn what is most useful.

A clear investment

Monthly engagements start at $10,000. The agreement sets out capacity, billing, and any separate tool or infrastructure costs.

Visible progress

One shared work queue, working releases, and regular priority reviews show what is happening and what comes next.

Room to adapt

As the first system goes into use, we can direct the next cycle toward improvements, broader adoption, or a new opportunity.

Working together

Senior help, inside the work.

With leadership

Choose where to invest.

Connect business priorities to practical opportunities, agree what success looks like, and make decisions as new evidence arrives.

With operators

Build around the real workflow.

Learn the exceptions, test useful output, and help the people doing the job become confident running the system.

With technical teams

Build and learn in the codebase.

Pair on production tasks, develop shared tools and review practices, and help internal engineers extend what gets built.

Common questions

What it is like to work with us.

Do we need a defined project?

No. A meaningful problem, executive sponsorship, and access to the people who understand the work are enough to begin the conversation. An assessment can help turn that into a prioritized first build.

How much time does our team need to contribute?

We agree that around the work. You need an internal owner who can help set priorities, provide context, and review results. Operators and engineers join the relevant working sessions so the system reflects their needs and they learn how to use it.

How do we know our team will actually use it?

Adoption follows visible usefulness. We build around work your people already own, with an internal owner involved from the start, so the system shows up in real tasks rather than in a training exercise. Pairing and working sessions continue through delivery, and low use tells us to change the build rather than push harder on the rollout.

How do you handle different skill levels on our team?

We meet people where they are. Engineers may pair on production tasks in their own codebase while operators begin by judging and improving output on a workflow they know well. Sessions are grouped so nobody has to learn alongside people working at a very different level.

What if our team is too busy to learn AI?

Most teams are. We carry the engineering while your people learn on work they already need done, which keeps the learning inside their day rather than adding a separate training commitment. We agree the time involved up front and keep it to the sessions that genuinely need them.

Can you build it for us?

Yes. We can carry the engineering while working with an internal owner, or pair closely with your developers. We choose a delivery approach that fits your capacity and how the system will be operated.

How long until we see real ROI?

We aim to get something into real use early rather than after a long build-up. Quiet Light’s outreach engine now runs in daily production, and Visiting Media’s assessment turned a large body of customer evidence into a prioritized roadmap. The larger return compounds after that, as your team applies the same pattern to more of its work.

How do you handle data access and security?

We agree where the work runs, which data it needs, and who can access it. We work with your technical team on scoped permissions and the hosting and AI accounts appropriate to the engagement, on business-grade platforms where your data is not used to train public models. Review requirements and operating controls are part of the build, and we can help write AI usage policy where you do not have one yet.

What does AI do, and what stays with a person?

We define that for each workflow. For example, Quiet Light’s outreach system researches buyers and prepares messages for an operator to review and send. We test against real examples and decide which actions need approval before expanding automation.

Who owns what gets built?

Under our standard terms, client-specific custom work becomes yours once the fees due are paid. Reusable FOG tools and methods remain licensed for use with the deliverables, and third-party components have their own terms. We make the operating setup and handover clear in the engagement. Read the full terms.

What happens when the engagement ends?

Our standard engagement is month-to-month, with 30 days’ written notice to end it. We provide reasonable transition assistance on request and agree the practical handover for the systems, accounts, and documentation involved. Your agreement sets out the applicable details.

What happens when we hire new people?

What we build comes with documentation, and the decisions behind it are written down as we go. We spread capability across the team rather than leaving it with one person, so a new hire can pick up a system without needing the person who first built it.

Are you Claude-only?

No. We are Claude certified because Anthropic is one of the strongest frontier labs, and that depth shows in how we use Claude Code, the Claude API, and the Claude Agent SDK. We also work extensively with OpenAI’s Codex, particularly 5.6 Sol and Astra, and use their image models heavily for visual work. We are expanding our use of Jev, where the typesafe model changes what you can depend on in production. We choose tools and infrastructure around the work, your environment, and how your team will use the result.

What happens when priorities change?

We update the shared queue, make the tradeoff visible, and agree what the next available capacity should address. Changes to the level of monthly investment are agreed together.

Your first opportunity

Tell us what you want to improve.

Let’s talk