Scoped

The CRM for software companies that ship what they sold

Every customer, every deal, and every build or implementation stays on one record, from the discovery call to go-live.

  • Set up in an afternoon
  • Free for one person
  • 30 days of Pro, no card
A man takes a phone call at his desk by a bright window, laptop open and a microphone beside it

Scoped is a CRM for software companies, dev agencies, and SaaS teams that sell a build or an implementation and ship it. It keeps the customer, each deal with its amount, the project a signed SOW or order form becomes with phases from kickoff to go-live, each scope decision as a comment on the phase it touches, and who owns the next step on one record. Sales, delivery, and the assistant you connect read the same page.

From the discovery call to handover, on one customer record.

In a CRM for software companies, the signature is the middle of the story, not the end. The deal, the project it becomes, and every scope decision in between stay attached to the customer, so sales, delivery, and your assistant all read the same page.

Answer the inbound lead before the next studio 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 dev agency already talks: Discovery call, Scoping, SOW sent, Signed. Selling a SaaS 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. The pipeline guide walks through naming them.

When last year’s client comes back for phase two, their customer page has the discovery notes, the SOW amount 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.

Next Tuesday. Monday night’s inbound lead is on the board by 9 and the reply goes out before standup. The engineers know the reminders moved to phase two, and your assistant knows the customer, not just the code.

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. Move the deal to Signed and Scoped offers the build as a project, filled in and linked to the customer, for you to confirm. Break it into the phases you actually run: discovery, design and prototype, build, user acceptance testing, launch, handover and training. Selling a SaaS product instead? 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’re a change request for 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 the work assigned to 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, and the customer keeps the history for version two.

Next Tuesday. The SOW you signed on Friday is already the project, 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.

Ask your assistant about the customer, not just the code

If your team already works with an AI assistant, connect it to your Scoped workspace and it can answer questions about the work you sold. Ask where the Wickhollow portal stands and what’s waiting on the client. Ask 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 what was promised at implementation and what’s still open. The assistant 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, a read-only connection can’t write at all, and you can revoke access anytime. Scoped doesn’t run the AI or meter its calls, and your record stays yours: export it anytime.

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.

What software companies and dev shops run on Scoped

The same record, set up for how a software development company sells and delivers: SaaS implementations onboarded, support retainers kept, discovery engagements scoped.

How studios, dev shops, and SaaS teams run it

A product studio, a B2B SaaS 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 SOW became the project with the client attached. Whoever picks up sees the first build, the change requests that were deferred, and who signs off.

  • Stages: Discovery call, Scoping, SOW sent, Signed
  • Each build runs discovery, design, build, user acceptance 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 SaaS 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: the closed deal becomes the implementation project on the same customer. Before the kickoff call, the onboarding lead reads what the account executive promised about data migration and admin 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 update 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?

Works with the assistants your engineers and account leads already use.

Connect ChatGPT, Claude, Grok, or Gemini to the one workspace you pick, and it works from the same customers and projects your team does. Bring your work over, and take it with you whenever you want.

Scoped

“Which quotes over $10K have gone quiet for more than a week?”

ChatGPT read the pipeline and left a follow-up note on two deals.

All integrations

Check the fit for your studio or software team.

Plain answers for owners and ops leads weighing a CRM that follows the work past the signature.

Can a CRM for software companies track the build after the SOW is signed?

Yes. Move the deal to your won stage and Scoped offers a project filled in with the customer and deal, which you confirm before it’s created. Break the build into phases with owners and status, and keep change requests as comments on the phase they touch. The deal-to-project guide walks through each step.

Does a dev agency CRM replace our issue tracker or time tracking?

Keep your issue tracker for code-level work. Scoped holds what sits around it: the customer, the deal, and the delivery phases you promised. It doesn’t track time, write proposals or SOWs, or collect signatures, so those stay in the tools you use today. The CRM and project management buying guide helps you map which tool does which job.

How do B2B SaaS teams run customer implementations in a CRM?

Track the sale through your demo and order-form stages, then turn the closed deal into an implementation project on the same customer. Give kickoff, data migration, configuration, admin training, and go-live each an owner, so the onboarding lead reads what sales promised. See how client onboarding runs, and compare plans for your team.

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

Start with the lead in your inbox and the SOW you signed last week; the rest follows as deals close.

Free for one person. 30 days of Pro on your first workspace, no card.