How to Pay Commission to Software Development Sales Person: The Complete Walkthrough (2026)
By Kushal Magar · May 4, 2026 · 13 min read
Key Takeaway
Pay software development sales reps 5–10% of total contract value on new logo deals, triggered by cash collected — not signed contract. Use a clawback clause for the first 90–180 days. Retainer expansions earn 3–5% monthly recurring for 12 months. The biggest mistake is paying on deal signing — project cancellations in software dev are common, and you will end up commissioning revenue you never collect.
TL;DR
- Commission rate: 5–10% of TCV for new logo project deals. 3–5% monthly recurring for the first 12 months on retainers.
- Payout trigger: Cash collected — not contract signed. Or split 50/50 across signing and first payment.
- Clawback: Require return of commission if client cancels within 90–180 days or invoice goes unpaid.
- Milestone billing: Pay commission installments as each milestone invoice clears — not upfront on the full TCV.
- Expansion: Separate commission rate for upsells and retainer growth — 3–5% of new MRR for 12 months.
- Biggest mistake: Paying on signed contracts. Software dev projects cancel. You will commission revenue that never arrives.
- Tools that help: CaptivateIQ, Spiff, Everstage, or a spreadsheet with clear formulas — the key is written rules, not the tool.
Overview
Paying commission to a software development sales person is not the same as paying a SaaS account executive. The deals are different — project-based, milestone-billed, longer cycles, higher cancellation risk. A commission plan built for SaaS applied to a dev shop creates misaligned incentives and expensive disputes.
This guide covers how to pay commission to a software development sales person from scratch: choosing the right model, setting rates by deal type, defining payout triggers that protect the business, writing a clawback clause, handling retainer commissions, and avoiding the mistakes that cause reps to game the plan or quit.
Whether you run a custom software agency, a nearshore dev shop, or sell development services as part of a broader GTM motion, this walkthrough gives you a repeatable commission structure you can document and implement this week. For broader context on building a sales strategy for a development business, that guide covers the full picture.
Why Software Dev Sales Commission Is Different
Software development sales operates on different economics than SaaS sales. Understanding the differences is the first step to building a plan that works.
Project-based revenue, not subscription. Most dev shop deals are scoped projects — fixed price or time-and-materials. Revenue arrives in installments, not as predictable monthly recurring. This means you cannot pay commission at contract close the way a SaaS company does.
High cancellation risk in early phases. According to PMI research, approximately 17% of large IT projects fail outright and another 43% face significant budget or scope overruns. A commission plan that pays on signing will regularly commission deals that cancel before delivery.
Long sales cycles. Enterprise custom software deals take 3–9 months to close. Your sales rep may be working a deal for six months with nothing to show in commission. The plan needs a draw or base structure that keeps reps financially stable through long cycles.
Deal size variance. A dev shop might close a $15,000 MVP build one week and a $500,000 enterprise platform the next. Flat commission rates work poorly across this range — you need tiered rates or deal-size brackets.
All of this matters when you design the plan. A generic software sales commission structure will not fit. The steps below address each of these factors directly.
Step 1: Choose Your Commission Model
Before setting a rate, choose the structure. Four models work for software development sales. Each has a different risk profile for the business and the rep.
| Model | How it works | Best for | Risk |
|---|---|---|---|
| Base + Commission | Fixed salary + % of each deal closed | Most dev shops — long cycles need base stability | Low for rep, medium for business |
| Commission-Only | Rep earns only on deals closed, no base | Freelance or part-time sales reps | High for rep, low for business |
| Tiered Commission | Rate increases as rep hits revenue thresholds | Shops with wide deal size variance | Medium for rep, medium for business |
| Residual / Retainer | Ongoing % of recurring monthly retainer revenue | Shops with dedicated team retainers | Low for rep, variable for business |
Base + Commission is the right choice for most dev shops. Software development deals take months to close. A commission-only rep who goes 90 days without closing will either quit or start cutting corners on qualification just to show activity. A base gives them financial stability to work long deals properly.
A typical base/variable split for a software dev sales rep is 60/40 — 60% base, 40% variable at OTE. This is more aggressive than a standard SDR plan (which usually runs 70/30) because closing custom dev deals requires more autonomy and risk tolerance. For comparison, see how commissioned SDR pay structures differ from closer-level compensation.
Step 2: Set the Right Commission Rate
Commission rates for software development sales vary by deal size and contract type. Use deal-size brackets rather than a flat rate to keep the math fair across your pipeline.
| Deal size (TCV) | Typical commission rate | Commission earned |
|---|---|---|
| Under $25k | 8–12% | $2,000–$3,000 per deal |
| $25k–$100k | 6–8% | $1,500–$8,000 per deal |
| $100k–$500k | 4–6% | $4,000–$30,000 per deal |
| $500k+ | 2–4% | $10,000–$20,000+ per deal |
These brackets reflect data from Glassdoor compensation reports and industry benchmarks shared across outsourcing and dev agency communities. Adjust based on your gross margin — custom dev margins typically run 30–50%, which leaves room for 5–10% commission without destroying profitability.
Sanity check: If your target OTE for the rep is $120,000 with a 60/40 split, the variable portion is $48,000/year. At a 7% rate, the rep needs to close roughly $685,000 in TCV annually to hit OTE. Build your quota backward from OTE, not forward from an arbitrary revenue target.
Understanding what B2B software sales actually looks like helps calibrate these numbers against your specific market and deal motion.
Step 3: Define Payout Triggers
The payout trigger is the event that unlocks commission payment. This is where most software development commission plans go wrong.
Never pay on contract signing alone. In software development, a signed contract is the start of a relationship — not proof that you will collect the money. Scope changes, disputes, and outright cancellations are common in the first 60 days of a project. Paying full commission at signing means commissioning deals that may never deliver revenue.
Three payout trigger models work for dev shops:
| Trigger model | How it works | Rep friendliness |
|---|---|---|
| Cash collected | Commission paid as each invoice is paid | Lower — rep waits for each payment cycle |
| 50/50 split | 50% at signing, 50% when first invoice clears | Medium — balanced upfront motivation and business protection |
| Invoice milestone | Commission released per project milestone invoice paid | Medium — aligns commission with project delivery rhythm |
The 50/50 split trigger is the most common choice for established dev shops. It gives reps a meaningful payment at close (enough to feel rewarding) while protecting the business against early-stage cancellations. Pair it with a clawback clause on the upfront 50% if the project cancels within 90 days.
Step 4: Handle Milestone Billing and Installments
Most software development projects bill in installments — discovery deposit, design milestone, development milestone, UAT, go-live. Your commission plan needs to account for this reality.
Two approaches work cleanly:
Option A — Pay on TCV at signing, clawback if project cancels. Pay the full commission on the total contract value when the contract is signed. Include a sliding-scale clawback: if the project cancels in month 1, rep returns 100% of commission. Month 2, 75%. Month 3, 50%. After 90 days, no clawback. This motivates reps to help ensure the project starts successfully.
Option B — Pay commission per milestone invoice cleared. Each time an invoice milestone is paid (e.g., $30,000 of a $150,000 project), pay commission on that installment. This ties rep earnings to project health — when the project stalls or disputes arise, rep commission also pauses, which naturally incentivizes reps to stay involved in client relationships post-close.
Option B is administratively heavier but creates better alignment. Most dev shops with 3+ active projects at a time find Option A simpler to manage and pair it with a robust clawback clause. Integrate this with your sales pipeline management process so milestone progress is tracked in the CRM alongside deal status.
Step 5: Write a Clawback Clause
A clawback clause is non-negotiable for software development commission plans. It protects the business against commissioning revenue that never materializes.
A clawback clause should specify four things:
- Trigger events: Client cancellation, client non-payment (invoice 60+ days overdue), project termination for cause, or scope rejection before work begins.
- Clawback window: Typically 90–180 days from commission payment. After this window, commission is vested regardless of project outcome.
- Clawback amount: Pro-rated based on revenue actually collected. If the rep earned $5,000 commission on a $100,000 contract and the client cancels after paying $40,000, the rep returns $3,000 (60% of commission on uncollected $60,000).
- Recovery method: Deducted from future commission payments — not demanded as a lump-sum repayment. Lump-sum demands create legal risk and destroy rep trust.
According to SHRM guidelines on sales commission agreements, clawback clauses are enforceable in most US states when they are clearly documented in a signed commission agreement. The clawback must be proportional — courts have rejected clawback clauses that tried to recover more than the commission paid.
Put the clawback clause in writing before hiring or promoting anyone into a closing role. A verbal understanding is not enforceable and will not survive a dispute.
Step 6: Commission on Retainers and Expansion
Software development agencies increasingly sell dedicated team retainers — a client pays a fixed monthly fee for a committed team of developers. This creates recurring revenue, and your commission plan needs to address it separately from project deals.
New retainer commission: Pay 3–5% of the monthly retainer fee for the first 12 months. On a $20,000/month retainer, that is $600–$1,000/month for 12 months, totaling $7,200–$12,000. Cap it at 12 months to prevent reps from collecting indefinitely on accounts they are no longer involved with.
Expansion commission: When a retainer client expands (adds more developers or increases scope), pay the new logo rate (3–5%) on the incremental MRR, not on the full retainer. A client who grows from $20,000/month to $30,000/month generates a new $10,000/month increment — commission applies to that increment only.
Renewal commission: Most dev shops do not pay renewal commission when a rep had no involvement in the renewal. If your rep actively renegotiated the contract or upsold scope, pay a reduced rate (1–2% of TCV). Passive renewals generate no commission — account management is not a sales activity.
This distinction between new logo, expansion, and renewal commission is essential for building a reliable sales forecast — each revenue category has a different commission cost that affects your gross margin projections.
Common Mistakes That Kill Motivation
These are the five commission plan mistakes that reliably lead to rep turnover, gaming, or disputes in software development sales teams.
1. Paying on signed contracts. Already covered above — but it bears repeating because it is the single most common mistake. Signed contracts in dev sales do not equal collected revenue.
2. No draw for new hires. A new rep joining a dev shop may take 4–6 months to close their first deal. Without a draw (advance against future commission), they cannot survive financially. Commission-only with no draw is a guaranteed way to lose good reps before they produce. Use a non-recoverable draw for the first 90 days.
3. Moving the goalposts after the deal closes. Changing commission rates, payout triggers, or clawback terms after a rep has already closed a deal is the fastest way to lose trust. Lock terms in writing before the year starts. Any mid-year changes apply to new deals only.
4. No attribution clarity. In dev shops, the founder often does the initial sales call, a technical lead handles scoping, and a sales rep closes the deal. Without clear written rules for split commission and attribution, every large deal becomes a dispute. Define attribution in your commission agreement: who closes the deal, who gets the commission, and how splits work when multiple people are involved.
5. Ignoring the cost of complexity. A commission plan with 12 variables and 6 edge-case rules is not motivating — it is confusing. Reps who do not understand their plan do not trust it and stop using it as a motivator. Keep the plan to 3–4 core rules. Every rep should be able to calculate their commission on any deal in under 2 minutes.
Tools That Help Track and Pay Commission
Commission tracking for software development sales does not require expensive software. It requires clean data and clear rules. The tool matters less than the process.
Spreadsheet (Google Sheets or Excel) — works for teams under 5 reps with clean CRM data. Build a formula that pulls deal value, applies the bracket rate, checks the payout trigger, and outputs commission due. Update monthly. The limitation is manual data entry errors and no audit trail.
CaptivateIQ — purpose-built commission management. Connects to Salesforce, HubSpot, and other CRMs. Supports tiered rates, clawback tracking, and rep-facing dashboards. Starting around $30/rep/month. Overkill for teams under 10 reps but excellent at 10+.
Spiff — real-time commission visibility for reps. Reps see their commission as deals move through the pipeline. Strong for high-velocity teams. More complex to configure than CaptivateIQ for non-standard deal types.
Everstage — gamified commission tracking with leaderboards and earnings projections. Better fit for larger sales teams where motivation mechanics matter alongside pure calculation accuracy.
For most dev shops with 1–5 reps: start with a well-structured Google Sheet. Move to a dedicated tool when manual tracking starts creating disputes or consuming more than 2 hours per month of admin time.
How SyncGTM Fits In
The hardest part of paying commission to a software development sales person is not the math — it is the attribution. Who sourced the lead? Which rep touched the account first? Which outreach triggered the inbound? When these questions do not have clean answers, every large commission payment becomes a potential dispute.
SyncGTM solves the attribution problem by enriching every lead that enters your pipeline with company firmographics, contact data, and source tracking — and syncing that enriched data to your CRM automatically.
When a deal closes, you can see exactly which rep sourced it, which touchpoints moved it through the pipeline, and how the account was enriched. This creates an auditable commission record without manual spreadsheet reconciliation.
For dev shops running outbound — where reps are actively prospecting lists, attending events, and sourcing accounts through LinkedIn — SyncGTM's enrichment and lead tracking eliminates the “who owns this account” disputes that plague small sales teams. See SyncGTM's pricing to find the plan that fits your team size.
Beyond attribution, SyncGTM helps your rep build a better sales pipeline by automatically enriching prospects with the signals that matter for software development sales: tech stack, team size, recent funding, hiring activity. Better prospect data means higher close rates, which means your commission plan actually pays out at OTE.