SaaS startup payroll: founder pay, stock options, and wages your tax credits ride on

Founder pay: nothing, salary, or an IOU — two of these are fine

Pre-funding, taking nothing is legitimate: no rule forces a founder to draw pay, and unpaid months create no filing obligations. Post-funding, a modest T4 salary through a real payroll account is the standard — it builds RRSP room, keeps CPP accruing, and reads as discipline in diligence. The bad option is the IOU: accruing founder salary on the books without paying it. An accrued bonus or salary unpaid 180 days after year-end loses its deduction in the year accrued, and a balance sheet carrying deferred founder comp is a red flag investors make you clean up at the worst possible moment.

Dividends rarely fit a startup — there is no profit to distribute and the cap table is built for growth, not yield. One EI nuance worth knowing: a founder controlling more than 40% of voting shares is EI-exempt, so a two-founder company usually pays no EI on founder salaries — but three equal co-founders each sit at about 33% and all three pay EI.

Stock options at a CCPC: the taxable benefit waits

For employees of a CCPC, exercising an option is not the taxable moment. The benefit — share value at exercise minus what they paid — is deferred until they sell the shares, which means no payroll withholding at exercise and no cash-flow trap from a paper gain. When conditions are met (options granted at fair market value, or shares held two years), the employee also claims the stock option deduction, taxing the benefit at half rates. The $200,000 annual vesting cap that limits the deduction at larger public and non-CCPC employers does not apply to CCPC options.

Payroll's unglamorous job is memory: grant dates, strike prices, exercise dates, and departures have to be tracked for years so that when an early engineer finally sells in an acquisition, the benefit lands on the right T4 in the right year. We keep the option ledger tied to the cap table so the exit-year slips are arithmetic, not archaeology.

Engineering payroll with the SR&ED claim in mind

Salaries are the backbone of most SaaS SR&ED claims, and the claim is only as good as the wage records behind it. Tag time at the source — sprint tickets and timesheets that mark experimental-development work — because reconstructing eligible hours in March for the prior fiscal year is how claims shrink under review. Pay design matters too: how you structure founder and engineer compensation changes what the claim can include.

Two consequences fall straight out of that table. Paying your core developers as contractors quietly shrinks the claim — 80 cents on the dollar and no proxy — on top of the usual classification risk. And a founder December bonus, natural everywhere else, is wasted money inside an SR&ED claim; we keep specified-employee comp as level salary instead.

Hiring US-based employees without breaking the structure

Your first US engineer can be hired in days through an employer of record, or properly through a US subsidiary running its own payroll on Gusto or ADP once a real US team is the plan. The payroll mechanics are the easy half; the hard half is what the hire does to the company — state nexus, permanent-establishment questions, and eventually the transfer-pricing arrangement between CanCo and USCo that investors will expect to see documented. Those decisions connect to the Delaware-flip question itself, which we work through in our cross-border guide for SaaS startups.

Whichever route you pick, remember the SR&ED table above: moving engineering headcount south moves those wages out of the claim. Plenty of startups keep R&D in Canada for exactly that reason and put sales hires in the US — a payroll map we help design alongside runway planning.

Source: CRA — SR&ED tax incentive program.