Scoped
Start free
Start freeLog in

The engagement you proposed is the engagement you deliver

Every proposal on one board, the signed engagement broken into workstreams, and the client’s whole history beside it. You, your associates, and your AI assistant work from the same record, so the Friday status starts from what actually happened.

Start free See the platformTalk to us
  • Set up in an afternoon
  • Free for 3 people
  • Associates open engagements on their phones
Two people at a wooden table mark up printed pages with a pencil, with open laptops on either side of the papers

From the intro call to the follow-on, on one record.

A consulting engagement is sold as a proposal, delivered as workstreams, and reported on every Friday. Scoped keeps the proposal, the engagement, and the client together, so the status note, the next proposal, and the client’s history all start from the same record.

Put every proposal on one board, and chase the quiet one first

A referral comes in on a Wednesday: a past client’s new COO wants help with the handoff between her sales team and operations. You add her to the board before the intro call, with who referred her, what she described, and when you’re speaking. Name the stages the way you already talk: Intro call, Scoping, Proposal sent, Signed.

The proposal still goes out from the document you write it in, and it gets signed wherever you sign today. Scoped keeps everything around it: the amount, the scoping notes, who owns the follow-up, and how long the card has sat without an update. The board shows what you have out and what it adds up to, which matters when you’re deciding whether to take the next call or protect next quarter.

The $48,000 operating-model proposal that has been quiet for eleven days sits on the board, not under a thread about calendar invites. When you follow up, the scoping note is on the card: the CFO who has to sign off, the board meeting it has to land before, the workstream they asked you to price separately.

Next Tuesday. Last week’s referral is on the board with the intro-call notes, and the proposal that went quiet gets a follow-up before your first client session.

See the sales pipeline

Try it: drag the $64,000 card to Signed.

Proposals on the board, with the amount on each card and the stages named the way a consultant says them.

Turn the signed proposal into the engagement, one workstream at a time

When the client signs, one click turns the proposal into the project with the client attached. Break it into the workstreams you proposed: kickoff and stakeholder interviews, the current-state map, operating model options, a pilot at one site, the leadership readout, the handover. Each has an owner and a status, so the associate running interviews and the consultant leading the pilot both know what is theirs, and nobody has to ask you.

Scope questions go on the workstream they touch. When the sponsor asks in week four whether the pilot can run at a second warehouse, the comment sits on the pilot, with the proposal amount at the top of the engagement. Whoever answers can see the proposed workstreams and that amount before they say yes, and the extra site becomes a change you price, not a favor you absorb.

Your Focus view shows only what’s waiting on you: review the interview synthesis, answer the sponsor’s question about the pilot, sign off the readout outline. Associates check their workstreams in the browser on their phones between client sessions. Hours and invoices stay in the tools you already keep them in; Scoped is the record of who owns what and what changed.

See Projects
In a meeting room, a woman points at columns of sticky notes on a whiteboard while a colleague stands back and listens
A signed engagement broken into workstreams, each with an owner and a status, with the client and the proposal amount at the top.

Write the Friday status from the week’s history, and see the follow-on coming

Every comment, status change, and scope question is recorded on the engagement with who made it. On Friday afternoon, the status note to your sponsor starts from that history: what finished this week, what moved, what is waiting on the client. You still send it from your own email. You just stop rebuilding the week from memory and three chat threads.

Follow-on work shows up inside the engagement long before anyone writes a proposal for it. The operations lead asks whether the new model could roll out to the other two warehouses. The CFO mentions next year’s pricing review during the readout. Put each one on the pipeline as a new deal on the same client while it’s fresh, with the note from the conversation, so the next proposal starts from what you already know.

When the handover is done, archive the engagement. The client’s page keeps every engagement, every workstream, and the starred note about how the sponsor likes to be briefed, ready for the next one.

See Clients
Hands type on an open laptop at a train table by the window, a phone lying beside it and green countryside blurred outside
An engagement’s activity: the week’s status from a connected assistant, recorded under the consultant who authorized it, above the team’s own updates.

Let your assistant draft Friday’s status from the record.

Connect Claude Code or Codex to your workspace and ask it about the real work: where each workstream stands before the Friday note, which proposals went quiet, and what you delivered for a client before you pitch them again.

  1. Summarize where the Northgate engagement stands this week and post it as a status comment.It reads each workstream and the week’s comments, then posts the status as a comment on the engagement, recorded under your name with the connection it came through.
  2. Which proposals have gone quiet for a week, and what did each client say mattered most in scoping?It reads the board and the client pages and lists each quiet proposal with its amount, how long it has been out, and the notes from scoping.
  3. Before my call with Halden Freight, list what we delivered for them and anything they said they’d want next.It pulls the client’s page and the archived engagement and answers with each workstream delivered, who ran it, and the follow-on ideas the team noted in comments.

You approve the connection for one workspace, and a read-only connection can’t change anything. Every update is recorded under the person who authorized it, and you can revoke access whenever you like. How assistant updates work.

The assistant’s update is recorded under the person who asked for it, with the connection it came through.

Your next engagement starts inside this one.

The follow-on tends to come up mid-engagement, in a sponsor’s aside or a question at the readout. When partners, associates, and your AI assistant answer from the same history, nobody pitches a client something you already delivered.

One record from first call to finished jobCustomers, quotes, and jobs live together. The won quote becomes the job with the customer attached, so nothing is retyped between the sale and the work.Your AI assistant, on the real workConnect Claude Code or Codex to the one workspace you pick. Every change it makes is recorded under the person who authorized it, and you can revoke it at any time.Your records stay yoursExport your whole workspace whenever you want it, with no ticket and no waiting. What an export contains, and what it leaves out, is documented.Priced for the business you runFree for three people, and your first workspace gets 30 days of Pro with no card. Paid plans are priced per workspace, not per seat.

Works with the assistant you already use between client calls.

Two named setup paths for AI assistants, each maintained and tested, plus your whole workspace to export whenever you want it.

Claude CodeAdd Scoped to Claude Code, sign in once, and it works in the one workspace you picked.CodexAdd Scoped from the Codex command line, then approve the connection in your browser.Bring your dataImport projects and issues from a supported CSV export, with a note of anything that didn’t come across.Export anytimeYour whole workspace, whenever you want it, with documented boundaries.Scoped ConnectComing soon: the desktop app that keeps your records on a database you control.
All integrations

Your client’s next project is already on somebody’s whiteboard. Make it yours.

Next Tuesday, every workstream on the Northgate engagement has an owner, the second pilot site is priced as a change before anyone says yes, and Friday’s status starts from the record instead of your memory. The rollout the operations lead mentioned in passing is already a deal on the client’s page. Scoped takes an afternoon to set up.

Start free Talk to us

Free for three people. 30 days of Pro on your first workspace, no card.

These choices apply only to scoped.ai. Optional analytics and advertising are off today. We’ll ask again before enabling them.

Privacy notice