stepbase

By team

The pipeline is half the job

Most sales tools model a pipeline and hand you off at the finish line. The part that actually pays — the thing you sold running for a term, coming to an end, and being sold again — ends up in a spreadsheet somebody remembers to open.

Build an app for freeBrowse templates

Won is not the end of anything

A deal closes and the record stops being maintained. The subscription it created lives in a different tab, with a renewal date nobody watches until the month it lapses. The discount that got the deal over the line was approved in a chat thread. And the account manager who inherits it has to reconstruct the whole history from email. None of these are CRM problems exactly — they are the problem that the pipeline and everything after it are two different systems.

Today

  • A pipeline tool for deals, a spreadsheet for renewals
  • Renewal dates noticed in the month they lapse
  • Discounts approved in a chat thread nobody can audit
  • A new account manager reconstructs the history from email
  • "What do they currently have with us?" takes three people to answer
  • Forecast numbers are a export somebody prepares on a Thursday

On stepbase

  • Deals and subscriptions on the same companies, in the same app
  • Renewals surface themselves: a schedule marks anything ending soon
  • A discount above your threshold starts an approval on its own
  • Every call, every approval and every renewal decision on the record
  • Open a company and see its people, its deals and what it currently has
  • Tiles read the live rows, so the number is current without preparing it

How it works

  1. 1

    Model what you sell

    Companies, the people in them, what you sell, the deals in play. A contact belongs to a company, a deal points at a company, a person and a product — so nothing has to be typed twice.

  2. 2

    Work the pipeline on a board

    Lanes come from the stage column's own options. Gate a lane on a checkbox and a deal cannot leave Proposal until the proposal is logged — the card is not draggable, with the reason on it.

  3. 3

    Let the renewals find you

    A schedule looks every morning for live subscriptions ending inside your window and marks them Due. That edit wakes a second Flow, which puts the call on whoever owns the subscription.

  4. 4

    Attach approvals to the column that triggers them

    Put a number in Discount and the approval starts by itself. Under your threshold it clears; above it, a manager decides on a clock. Whatever they decide is written back onto the deal.

Start from a template

Every template is fully editable: change the stages, forms, and routing to match how you work.

CRM

Companies, the people in them, what you sell, the deals in play, plus the subscriptions, renewals and approvals that come after you win.

View template

What makes it work

Tables & recordsColumns, links, rollups, views, policiesPages & boardsRecord pages, boards, tiles, public linksAutomationsSchedules, row changes, webhooks, waits, connectorsAnalytics & auditTiles, charts, cycle time, the audit trail

FAQ

Common questions

Not for a large sales org with a dedicated admin. It is a good fit for a team whose pipeline currently lives in a spreadsheet, or one whose real problem is what happens after Won — renewals, approvals and account history that a pipeline tool leaves to somebody's memory.
Yes. A product here is whatever you sell for a period: a placement, a plan, a licence, a retainer, a room. If your business is find someone, agree a term, deliver it, renew it, the shape fits.
Yes, and the board follows. Lanes are the stage column's options, so adding or renaming one changes the board, the charts and the filters at once — there is no second copy of the stage list anywhere.
From a change to a column, not from a form. Entering a discount on a deal wakes a Flow bound to that row; it clears itself under your threshold and goes to a manager on a clock above it. The decision is written back onto the deal and listed on its record page.
Yes. A row policy on the table narrows it to the rows somebody owns, enforced on every surface that renders data on their behalf — the grid, the board, the tiles and the record page.

What process would you turn into an app?

Build it free, or start from a template and change what you like. No credit card, no setup fees.

Start from a template