Scoped

The CRM for software companies that ship what they sold

Every customer, every deal, and every build or rollout on one record, from the discovery call to go-live. Connect Claude Code or Codex, and the assistant that knows your codebase knows the customer too.

  • Set up in an afternoon
  • Free for 3 people
  • Works with Claude Code and Codex
A man takes a phone call at his desk by a bright window, laptop open and a microphone beside it

From the discovery call to handover, on one record.

The deal, the project it becomes, and every scope decision in between stay attached to the customer, so sales, delivery, and your connected assistant all read the same page.

Reply to the lead before the next name on their shortlist does

Say a founder emails on Monday night: they need a mobile app MVP live before their spring launch, and you’re one of three studios they wrote to. By 9 on Tuesday someone has added them to your board in Discovery call, with what they need, who referred them, and who is replying. The reply goes out before standup, not after the other two.

Name the stages the way your team already talks: Discovery call, Scoping, SOW sent, Signed. Selling a product through demos? Make it Demo, Technical review, Order form out, Closed won. Each deal carries its amount, so the board shows what you have out and that the $38,500 data migration has gone quiet for eleven days.

When last year’s client comes back for phase two, their page has the discovery notes, the deal you signed and what it covered, the project you shipped, and the starred note about who actually signs off. You scope the next build from what you know, not from a blank doc.

See the sales pipeline

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

The pipeline, with the stages named the way a software studio says them.

Turn the signed SOW into the build, phase by phase

The $86,000 customer portal for a veterinary group gets signed. One click turns the won deal into the project, with the customer attached. Break it into the phases you actually run: discovery, design and prototype, build, client testing, launch, handover and training. Each has an owner and a status. Selling software instead of building it? The same shape holds for an implementation: kickoff, data migration, configuration, admin training, go-live.

Scope moves. On Thursday’s call the client asks for text reminders at launch, and you agree they belong in phase two. That decision goes on the build phase as a comment the team sees, not in a call recording nobody replays. Six weeks later, when their new ops lead asks why reminders didn’t ship, the answer is on the project.

Your Focus view shows only what’s waiting on you: the client’s login decision, the testing sign-off, the handover notes. On Plus and Pro, cycles keep a two-week push honest, and on Pro, initiatives group a customer’s portal, integration, and support work together. When the build ships, archive it. The customer keeps the history for when they call about version two.

Next Tuesday. The deal you signed on Friday became the project in one click, every phase has an owner, and nobody has to ask sales what was promised.

See Projects
Two colleagues talk in front of a whiteboard covered in flowchart and wireframe sketches drawn in red marker
A signed customer portal broken into delivery phases, each with an owner and a status, with the customer linked at the top.

Put Claude Code or Codex on the customers, not just the code

If your engineers already spend the day in Claude Code or Codex, connect it to your Scoped workspace and the same assistant can answer questions about the work you sold. Ask it where the Wickhollow portal stands and what’s waiting on the client. Ask it which signed deals haven’t had a kickoff, or which builds have gone a week without a comment.

Before a renewal call, your account lead asks it what was promised at implementation and what’s still open. It pulls the customer’s history, the deal, and the project’s phases, and answers from the record instead of from someone’s memory of the kickoff.

It can post a comment or update the fields you allow, like a phase’s status or the next step. Each change is recorded under the person who authorized it and the connection it came through, and a read-only connection can’t write at all. Scoped doesn’t run the AI or meter its calls. How assistant updates work.

See AI assistants
An engineer in orange headphones works at a desk with code on two monitors and a laptop beside high-rise windows
A project’s activity: the assistant’s note on client testing, recorded under the founder who authorized it and the connection it came through.

How software teams like yours run it

A product studio, a software company, and a development shop: their stages, how a project breaks down, and what they ask their assistant.

The phase-two call, answered on the first ring

A nine-person product studio

Say a founder whose mobile app the studio shipped last year calls about phase two. The discovery call went on the board the day it happened, and the signed build became the project with the client attached. Whoever picks up sees the first build, the features that were deferred, and who signs off.

  • Stages: Discovery call, Scoping, SOW sent, Signed
  • Each build runs discovery, design, build, client testing, launch, handover
  • The founder asks: which past clients have deferred features we could scope as phase two?

Implementations that start where the sale ended

An eight-person B2B software company

The company sells field inspection software to facilities teams through demos and order forms. Say a facilities team signs the order form on Friday: one click turns the closed deal into the implementation on the same customer. Before the kickoff call, the onboarding lead reads what the account executive promised about data migration and training.

  • Stages: Demo, Technical review, Order form out, Closed won
  • Each implementation runs kickoff, data migration, configuration, admin training, go-live
  • The onboarding lead asks: which implementations are stuck on data migration, and who owns each?

Retainer clients who hear from you first

A five-person development shop

The shop maintains apps for a handful of retainer clients, and each retainer is a project that runs in two-week cycles. Say a client reports a checkout bug on Tuesday: it goes on the phase it touches as a comment. On Friday, the lead writes each client’s note from the record, not from memory.

  • Stages: Inquiry, Code audit, Proposal out, Retainer signed
  • Each cycle runs triage, fixes, release, client update
  • The lead asks: what did each retainer client raise this cycle, and what shipped?

The founder is still choosing a studio. Reply before standup.

Next Tuesday, someone adds Monday night’s inbound lead to the board by 9, and the reply goes out before standup. The engineers know the reminders moved to phase two. Your assistant knows the customer, not just the repo. Scoped takes an afternoon to set up.

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