The crew

Seven douu. All of them yours.

douu starts you with a crew rather than a blank box. Each one has a narrow brief, its own schedule, and its own entry in My douu — and you can fire any of them, rename them, or make new ones from skills.

Get the crew

douu
Everything
Always on, on your machine

douu is the front door. You describe the outcome — "get me ready for Shanghai", "close the quarter" — and douu works out which jobs exist, which of its crew should take them, and what it needs from you. Everything it does lands in one activity log you can read top to bottom.

What it does

  • Chat, phone or email in
  • Delegates to the crew
  • Holds the plan you can edit

Ask it

“Sort the week, hand the rest to the crew, and keep you posted when something needs a human.”

Tally
Sales
Weekdays, 08:30, before standup

Tally lives in the CRM and the inbox at the same time. It reconciles the two, so the number in the standup is the number in the system, and any deal that has gone quiet gets a draft follow-up sitting in your outbox — never sent without you.

What it does

  • CRM + inbox reconciliation
  • Draft follow-ups, never auto-send
  • Pipeline sheet in your own template

Ask it

“Pull the pipeline, chase what went quiet, and have the numbers on your screen before the standup.”

Deck
Decks & docs
On request, or on a schedule you set

Deck is the one that carries things. Ask for the Q3 review and you get the deck, the two-page summary and the workbook behind it, all built on your company template so it does not look like it came from a robot.

What it does

  • Deck + report + workbook together
  • Your template, your fonts
  • Editable files, not screenshots

Ask it

“Turn a sentence into the slides, the report and the workbook that go with it.”

Scout
Research
Weekly, on the day you choose

Scout reads for you and shows its work. Every sentence in a Scout brief carries the page it came from, because a claim you cannot check is a claim you cannot use.

What it does

  • Watches markets and competitors
  • Source on every claim
  • Two pages, not a firehose

Ask it

“Watch a market every week and send you the two pages that actually changed.”

Momo
Meetings
Every meeting you invite it to

Momo joins with your permission, writes minutes with a name against every action, and then puts those actions where they belong — the ticket tracker, the CRM, the calendar — instead of leaving them in a document nobody opens.

What it does

  • Pre-read briefing
  • Minutes with owners
  • Actions filed in your tools

Ask it

“Sit in the call, take the minutes, and put the actions where the work already lives.”

Quill
Writing
On request

Quill reads what you have already written before it writes anything, and it keeps a notes file of the people, places and rules in your work so chapter twelve does not contradict chapter two.

What it does

  • Voice matching from your archive
  • Continuity notes for long work
  • Rewrites you can diff against the original

Ask it

“Hold your voice: drafts, rewrites and long-form that still sounds like you wrote it.”

Pip
Money
On request

Pip is built to argue with you. It models the decision you are about to make, runs the dull scenarios, and when the plan only works if everything goes right, it says so in the first line.

What it does

  • Costs and scenarios in one sheet
  • Assumptions written down
  • An entry in the log when it disagrees

Ask it

“Model the decision before you make it, and say plainly what it costs you.”

Made, not hired

Every skill you add becomes a douu.

The crew above is the starting seven. The eighth is the one you build, and it takes about a minute: pick a skill, give it a name, tell it what a good result looks like.

  • Built on the same engine as the starting crew
  • Narrow brief — it only does the one job
  • Shares the log, the approval gate and the permissions you already set

Build one now

Ledger
Valuation
Created from the Valuation skill

Ledger was not hired, it was made. Someone in this account added the Valuation skill and douu built a douu for it — same engine, narrower job. It reads the books, builds the model, writes the memo, and lists what it could not verify.

  • Reads the sources you point at
  • Model plus written memo
  • Confidence and gaps stated up front

Everyone takes a piece.

Hand a job to three douu and read the thread, not a status report.

One thread. Three specialists. The artifacts at the top.

Give them something to do.

Install, connect three apps, and hand over the first job.