When should a startup hire its first salesperson?

When you have repeatable discovery, a price that closes, and more qualified conversations than the founder can run alone — not when you are hoping someone else will invent the motion.

What should be ready before a first sales hire starts?

Named pipeline stages with definitions, org email on customer records, proposal templates beside deals, a weekly pipeline review ritual, and clear rules for what must be logged before a demo is marked complete.

Should the first sales hire use the founder's personal Gmail?

No for customer-facing work. Buyers should see a company address, and threads should live on the opportunity so the team can cover for each other. Personal inboxes are fine for investor mail if your policy allows.

Is Salestrics ready for a first sales hire?

Platform status is Live as of July 10, 2026. Teams use Free Forever to test, then add seats on Startup or Launch when the hire starts. Check System Status for current shipping cadence.

← Back to Blog

July 24, 2026 4 min read Salestrics Team

Before Your First Sales Hire: What to Set Up This Week

You posted the job. Maybe you already have a short list. The trap is assuming your new rep will figure out how you sell — the Gmail labels, the Drive folder called FINAL v7, the pipeline stages you invented in March. They will not. They will mirror whatever is visible on day one, including the chaos you stopped noticing. This checklist is what to fix before your first sales hire logs in — not a 90-day onboarding deck.

Why week-one setup matters more than week-one training

Training teaches skills. Setup teaches habits. If your first rep learns to send proposals from a personal Drive folder because that is what you did, you have duplicated yourself — including the parts that do not scale. If they learn to work from the opportunity record — mail, notes, docs, next step — you have bought leverage.

You do not need a RevOps hire for this. You need an afternoon and a decision to stop treating revenue tools as the founder's private notebook.

1. Write down your stages (in plain English)

Open your CRM and read each stage name out loud. If any answer to “what has to be true to move here?” is “uh, vibes,” fix it before Monday.

Seed teams usually need no more than six stages: qualified, discovery, demo, proposal, negotiation, closed. Under each, one sentence: what changed, who was in the room, what document exists. Put this in a doc your hire reads on day one — not buried in Notion page fourteen.

Momentum CRM lets you enforce required fields on stage change. Use that sparingly — two or three fields, not a tax form. The goal is shared language, not activity theater.

2. Move customer email off the founder's inbox

Your hire cannot cover your deals if buyers only reply to founder@personalmail.com. Set up org email before they start. Forward existing threads onto the right opportunities or re-introduce yourself from the company domain on open deals.

Salestrics Mail ties threads to opportunities — when the founder is on a flight and the buyer replies, the rep sees it on the record. That is not a nice extra. It is how a two-person team behaves like a team.

3. Put one proposal template where the deal lives

Not twelve versions in Drive. One template in Workspace beside the opportunity: scope, pricing table, assumptions, signature block. When your hire clones it for Acme, you can review diffs without a Slack thread asking “which file?”

Founders often resist this — the proposal is where they express craft. Fine. Express craft once in the template, then let the hire customize the three cells that change per deal.

4. Decide what “demo done” means

Write it down: demo is not complete until recap email is sent, next meeting is booked or a clear no is logged, and economic buyer is named or marked unknown. Your hire should never wonder whether a stage advance is optional.

If you use Connect for demos, note that on the opportunity. If you still use an external video tool, say so — and require a three-line summary on the record within an hour. Memory is not a system of record.

5. Run one pipeline review the way you expect them to

Before the hire starts, run your weekly review in the tool they will use. Thirty minutes: commit vs best-case, stuck deals, one decision per stuck deal. If you cannot do it without exporting to a spreadsheet, fix data entry first.

6. Permissions and money fields

Decide who can discount, who can delete opportunities, and who sees finance fields. A first hire should not need admin keys. They should see pipeline, mail on their accounts, and templates — not billing configuration.

If you use Ledger, confirm whether the hire needs read access for deal sizing or whether that stays founder-only until you have a second manager.

7. What the founder must stop doing

The hardest item on the list. You cannot run every call and also evaluate a hire. Pick a lane for the first 30 days:

Founder owns enterprise or founder-led accounts; hire owns inbound and SMB.
Founder joins discovery on the hire's deals — not the other way around on every call.
Founder stops sending one-off pricing from memory; pricing comes from the template.

If you skip this, you will hire a rep and remain the bottleneck. The CRM will look busy. The number will not move.

Day-one agenda (one page)

Give your hire a single page: stage definitions, where mail lives, where proposals live, how to book internal help, and the pipeline review calendar invite. Walk one live opportunity together — from inbox to next step — in under twenty minutes. That beats a two-hour tool tour.

Platform status is Live (July 10, 2026). If you are still testing, start on Free Forever this week so the record is not empty when they arrive. Track releases on System Status.