How to

How to build a sales CRM

Most CRMs are configured into shape over years, and reps still keep the real pipeline in a spreadsheet. Here is the model behind one built around how your team sells, the prompts to build it, and what it takes to run it.

The short answer

A sales CRM is five parts: accounts and contacts as separate records, deals that move through stages with a probability and a close date, an activity log against all three, a forecast by owner and stage against quota, and a home screen that tells each rep what to do next. The record keeping is the easy part. The work is making the next step, the close date and the amount honest, because a forecast is only as good as the deals reps bother to update. Build it so updating a deal is quicker than not updating it.

customer-relationship-management.helix-app.ai

Customer Relationship Management

4.2M

Open pipeline

1.1M

Commit this quarter

68%

Closed against quota

6

Deals with no next step

Discovery9

Brightsea

135K · close 30 Nov

Fenwick

48K · close 12 Dec

Proposal6

Kestrel Ltd

64K · next step tomorrow

Negotiation4

Halden Foods

410K · no next step

Commit3

Northrise

240K · close 28 Nov

Vantor

88K · close date passed

A sketch of the deal board. Two cards are flagged, and neither for its size: one has no next step and one has a close date in the past, which are the two things that quietly break a forecast.

What matters here

  • A sales CRM is five parts: accounts and contacts, deals with stages, an activity log, a forecast against quota, and a home screen built around next steps.
  • Keep accounts and contacts as separate records. People change jobs, and a contact stuck inside one account record leaves with them.
  • Every open deal needs a next step and a date. A deal without one is not pipeline, it is hope, and the app should say so.
  • Forecast by owner and stage against quota, on your fiscal calendar. A forecast on calendar quarters when your year starts in February is wrong every quarter.
  • An agent that reads the deal, its activity and its contacts can suggest the next step. A person confirms it before anything saves.
  • The CRM holds every customer relationship you have, so SSO, scoped access and managed credentials are part of the build, not an afterthought.

Who this is for

You run sales, revenue operations or a sales team. You know your stages and your fiscal calendar. What you want is a CRM your reps actually update, with a forecast you can stand behind, without a year of configuration first.

How it works in practice

What a rep and a sales leader each do, and why the next step is the centre of the design.

  1. 1

    A rep opens on their next steps

    Overdue and upcoming activities first, then their deals. The home screen answers what do I do today, not how big is the pipeline.

  2. 2

    Moving a deal is one drag

    Drag a card to the next stage and the app asks for the next step and the close date in the same moment. Updating is quicker than leaving it.

  3. 3

    Every call and email lands on the timeline

    Activities attach to the account, the contact and the deal at once, so the history is in one place whichever record you open.

  4. 4

    The agent suggests what comes next

    Ask the deal coach about a deal and it reads the stage, the activity and the buying committee, then suggests a next step. The rep confirms it or ignores it.

  5. 5

    The forecast builds itself

    Commit, best case and closed won by owner and stage, against quota, on your fiscal quarter. Nobody rolls it up in a spreadsheet on Thursday night.

  6. 6

    Leaders see the deals that need attention

    No next step, close date passed, or stuck in a stage longer than usual. A short list to ask about, rather than a pipeline review of every deal.

What a sales CRM is made of

A sales CRM is not a contact list with a pipeline view. It is five parts, and the last one decides whether the other four stay up to date.

Accounts and contacts

Companies and people as separate records, linked by role. Each account carries its owner, its region and industry, and for customers the plan, ARR, renewal date and health.

Deals with stages

An amount, a stage, a probability, a close date, a competitor and a next step, owned by one rep. Stages mean something specific in your sales process, and the app enforces what each one needs.

An activity log

Calls, emails, meetings and tasks with due dates, each attached to an account and optionally a contact and a deal. Append only, so the history can be trusted.

A forecast against quota

Commit, best case and closed won for the current fiscal quarter, by owner and by stage, against each rep's quota. Calculated from the deals, never typed in.

A home screen built on next steps

What each person should do today: overdue tasks, upcoming meetings, deals with no next step. This is what makes reps open the CRM rather than update it once a week for the forecast call.

These prompts start from a Helix project, which is what handles sign-in, credentials and hosting. Start with Helix

The prompts

Paste these into Claude Code, Codex or Cursor in order. Each one leaves you with something that runs, so you can stop after any step.

  1. Accounts, contacts and deals

    The records everything else hangs off.

    Create a Helix app: a sales CRM.
    
    Keep accounts and contacts as separate records. An account is a customer
    or a prospect, with an owner, region and industry. Customers also carry
    their plan, ARR, contract and renewal dates, and a health score. A contact
    belongs to an account and has a role, an email and a last touch date.
    
    A deal belongs to an account and has an amount, a stage, a probability, a
    close date, a competitor, an owner and a next step with a date. Keep the
    stages and their default probabilities in one editable file.
    
    Give me a searchable table of accounts I can filter by type, region,
    industry, owner and health, and an account page that shows its contacts,
    its open deals and everything that has happened with it.
  2. The deal board and the next step

    Making an honest update quicker than no update.

    Now a deal board with a column per stage. Drag a card to change its
    stage, and when someone does, ask for the next step and the close date
    in the same small form, prefilled with what is there now.
    
    Flag any open deal with no next step, a next step date in the past, or
    a close date in the past. Show those flags on the card and count them on
    the overview.
    
    Open a deal to edit the amount, probability, close date and next step,
    and record each change on the deal's history with who made it and when.

    Worth knowing. Asking for the next step at the moment a deal moves is the cheapest data quality control a CRM has.

  3. Activities and the home screen

    Why a rep opens the CRM in the morning.

    Let me log a call, email or meeting against an account, a contact or a
    deal, and add tasks with due dates. Show every activity on a timeline on
    the account page, newest first.
    
    Make the overview open on the signed-in person's next steps: overdue
    tasks, what is due this week, and their deals with no next step. Then
    the numbers: open pipeline, this quarter's commit and best case, and
    closed won so far against quota. Every number links to the list behind
    it.
  4. A forecast on your fiscal calendar

    The number a sales leader is asked for every week.

    Add a forecast for the current fiscal quarter. Our fiscal year starts on
    1 February. Show commit, best case and closed won by owner and by stage,
    against each owner's quota, and roll the owners up by manager.
    
    Calculate everything from the deals. Nobody types a forecast number in.
    Show which deals moved in or out of commit since last week, because that
    is the first question on every forecast call.
  5. Add a deal coach agent

    An agent where the deals already live, which suggests and never saves.

    Add a Helix agent called the deal coach. On a deal page, a rep can ask it
    what to do next.
    
    Give it read-only tools for the deal, its account, its contacts, its
    activities and its stage history. It should suggest one next step with a
    date, say what in the record it is based on, and point out any risk it
    sees, such as no contact above manager level or no activity for three
    weeks.
    
    It never saves anything. Show its suggestion with a button that fills the
    next step field, and the rep decides whether to keep it.

    Worth knowing. The agent reads through tools that only read. A person confirms every change, so the record stays something the team wrote.

  6. Connect it to real systems

    The step that turns a working prototype into something with your data in it.

    Now connect it to the systems we actually run, so it works on real data
    rather than the rows you seeded.
    
    Anything in angle brackets is a placeholder. Swap it for whatever we use
    instead, and have the app name the connection it wants rather than assume
    a vendor, so changing my mind later is a config change and not a rewrite.
    
    <Google Workspace>. Read sent email and calendar meetings with known
    contacts, so activities log themselves instead of relying on reps.
    
    <Gong>. Read call summaries and next steps, which are often the most
    honest record of where a deal stands.
    
    <HubSpot>. Read new leads and their campaign history, so a rep can see
    how an account found us.
    
    <Stripe>. Read what each customer pays today, so account ARR comes from
    billing rather than from a field someone typed.
    
    <DocuSign>. Read when a contract is signed, which is the moment a deal is
    really closed won.
    
    <Okta>. Read teams and managers, so each rep sees their own deals and each
    manager sees their team's.
    
    <Snowflake>. Land deals, stage changes and activities beside the rest of
    our data, so win rates and cycle times become a query.
    
    Only write where I have said to write. Everything else is read only.

    Worth knowing. Every name in angle brackets is a placeholder for whatever you run. Helix holds the credential as a workspace authentication, so the app references an alias and never the secret itself.

  7. Ship it

    The last step of every build: a URL, and the right people on it.

    Deploy my app.

    Worth knowing. Your assistant runs helix deploy underneath and the app comes back as a URL. Set Access Control before sharing: reps see their own deals, managers see their team's, and sales leadership sees everything.

What it connects to

A CRM sits in the middle of the sales stack. Most of what makes it useful arrives from somewhere else.

  • Google Workspace

    Read sent email and calendar meetings with known contacts, so activities log themselves instead of relying on reps.

  • Gong

    Read call summaries and next steps, which are often the most honest record of where a deal stands.

  • HubSpot

    Read new leads and their campaign history, so a rep can see how an account found you.

  • Stripe

    Read what each customer pays today, so account ARR comes from billing rather than from a field someone typed.

  • DocuSign

    Read when a contract is signed, which is the moment a deal is really closed won.

  • Okta

    Read teams and managers, so each rep sees their own deals and each manager sees their team's.

  • Snowflake

    Land deals, stage changes and activities beside the rest of the company's data, which is what turns win rates and cycle times into a query.

Each line says whether the app reads, writes or both. Anything not described as writing should be read only.

Named systems are the ones most teams actually run, not a list of the only ones that work. Swap in whatever you use.

Each connection is an authentication in your Helix workspace, referenced by alias. The app names the connection it wants and never holds the credential, so nothing here ends up in your code and any of it can be rotated or revoked without a redeploy.

Running it for real

The build gets you a working CRM. It holds every customer relationship you have and the number the board asks about, so it needs to be run properly.

AI Deployment

Get it to a URL people can open

One command takes the app from your assistant to a live address, so the sales team gets a link rather than instructions for running it locally.

App Security

Put your identity provider in front of it

Reps sign in with their existing account, and access follows the org: a rep sees their own deals, a manager sees their team's.

App Security

Connect your systems with managed credentials

Reading email, calls and billing needs real access. Granting it to the app rather than pasting a key into it means it can be rotated or revoked without a redeploy.

App Registry

Put a name on it

Every app carries a named owner and an entry IT can see, so the CRM does not become nobody's problem when the person who built it changes role.

Questions people ask

What should a sales CRM include?

Accounts and contacts as separate records, deals with stages, an activity log, a forecast against quota, and a home screen built around each person's next steps. The first four are records. The fifth is what keeps them up to date.

Why do reps stop updating the CRM?

Because updating it is slower than not updating it, and nothing in it helps them that day. Ask for the next step at the moment a deal moves, open on what to do today, and log activities from email and calendar automatically.

How should a CRM forecast work?

Calculated from the deals, never typed in: commit, best case and closed won for the current fiscal quarter, by owner and stage, against quota. Use your fiscal calendar, and show what moved in or out of commit since last week.

How is this different from a lightweight CRM?

A lightweight CRM is for teams whose relationships do not belong in the sales CRM, such as partnerships or recruiting. A sales CRM runs your pipeline and your forecast, so it carries stages, quotas and the deal history a revenue team needs.

Can an AI agent work inside the CRM?

Yes. A Helix agent can read a deal, its activity and its contacts through read-only tools and suggest a next step or point out a risk. Keep it read only and have a person confirm any change, so the record stays something the team wrote.

Can I build this without an engineering team?

Yes. The prompts here are written for Claude Code, Codex or Cursor and stage the build. The judgement calls are your stages, your fiscal calendar and what counts as commit, and none of those is something a tool can decide for you.

Tray.ai

Integration and automation guides

Build the integrations that keep it fed

An app is only as good as the data in it. These build the integrations and automations that keep this one current, on the Tray platform. Same kind of guide, same kind of prompts.

Last reviewed November 2026.

Build it, then run it properly

Helix runs the apps and agents you build. Deploy what you build, put SSO in front of it, connect it to your systems with managed credentials, and give it a named owner.

Want to talk to someone first? Contact us