# Pair Building for Teams

## Who this is for

- Small teams and SMEs that know what they want to say but can't get it out
  the door: the newsletter, blog, and social presence that stall on
  formatting and logistics, not on ideas.
- Organisations where publishing depends on the one colleague who knows how
  the tools work, and everyone else's finished work queues behind them.
- Teams that want their people building the system themselves rather than
  receiving one they had no part in.

## Problem

- The blockage is rarely creative. Between a finished draft and a published
  thing sit twenty technical steps: photos resized, video cut, HTML email
  that renders, LinkedIn formatting, the content calendar, pushing to the
  right channel at the right time.
- That layer lands on whoever happens to know how, until they become the
  bottleneck, and much of the work simply never ships because nobody could
  face the formatting.
- AI is genuinely good at exactly this layer (converting, formatting,
  sizing, scheduling, publishing) without touching the team's ideas or
  voice.

## What we do

- Full working days, on site or remote, with the whole team at keyboards.
  Aisling navigates; the team drives.
- Morning: trace where finished work gets stuck on its way out, with the
  team. Midday: build the foundation: shared context file, folder
  structure, formatting templates, plain-language rules for what can go
  where. Afternoon: each person builds the pipeline that takes their
  finished work to a published thing. Close: write everything down, assign
  ownership, agree what to try before any follow-up day.
- Price, published: €1,800–€3,000 + VAT per working day, quoted per
  organisation by team size, preparation, and scope. One day, one price, the
  whole room; never per seat. Most teams book one day, use it for a
  fortnight, then decide about a second.

## Outcomes

- A shared context file every person's AI reads; the voice stays the
  team's; the machinery just knows it.
- Publishing pipelines per channel: finished draft in, published thing out:
  HTML email that renders everywhere, LinkedIn-ready formatting, images
  sized per platform. Built by the person who runs each one.
- A content calendar that actually runs: what goes where when, plus the
  routines that do the pushing.
- A one-page usage policy the team wrote and therefore follows, and a record
  of who took part and what was built: the documented, proportionate effort
  European rules increasingly expect.

## How we work

- Quoted per organisation after a short exchange about team size and the
  work. The quote names what would be built, in what order, and what the team
  should be able to do without Aisling afterwards.
- If a day is not needed, that is said plainly instead of quoted.
- Individuals and one-person businesses have their own track with published
  package prices at /pair-building/.

## Next step

- Write via /contact/ with team size, the nature of the work, and the task
  that eats the most collective time.