A twelve-year-old time-tracking SaaS at an eight-figure run rate, run by about 200 people in roughly 43 countries with no office at all — and with an async operating model that lets it carry half the management layer a comparable on-premise company needs
around 25% growth in 2022 · roughly 195% growth in 2020 · about 200 people across about 43 countries (all founder-reported, August 2022)
"The managerial level inside of asynchronous organizations is 50% thinner than their on-premise counterparts." More people doing the work, fewer people managing people — that is the actual economic case for async, and a company paying for an office cannot copy it.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Liam Martin has co-run Time Doctor, a time-tracking SaaS at timedoctor.com, for twelve years at the point of this August 2022 interview with Rob Walling. The numbers he is willing to share: team members in about 43 different countries, "a nice reliable eight-figure run rate," growth he expects to land around 25% for the year, and roughly 200 people in the organisation. The outlier year was 2020 — "I think we did like 195 growth" — when the time-tracking category was hit by every company on earth going remote at once. He describes the experience without flattery: "it was literally like you know those big tubes where they put like 20 bills… that was the first couple months of covid for us." He also says he made a lot of wrong moves in that window, and names the companies that got it right — Loom and Mural, both of which went freemium almost immediately because they understood the prize was attention for the whole remote stack rather than monetisation of that quarter. The demand was that indiscriminate: he took a phone call from a G20 country that had moved 540,000 employees remote the previous day and wanted to know what to do next. "I said I have no idea, we have like 200 people in our organization, why don't you talk to somebody else — and they said you're the first guy that picked up the phone." The reason this company is worth a file on a directory of copyable businesses is not the product, which is ordinary, but the operating model. Martin's book Running Remote came out the day this episode published, and its argument is that asynchronous work is not remote work with extra steps — it is a different cost structure. His own research found async organisations carry a management layer 50% thinner than comparable on-premise companies, and that the async companies he interviewed averaged an employee net promoter score of 72 against an industry average of 36.
Time-tracking software is bought by the person who signs the invoices, not the person whose time gets tracked, and that single fact determines where the first customers come from.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Podcast interview: Startups for the Rest of Us, episode 616, published August 2022, Rob Walling interviewing Liam Martin on the day his book Running Remote was released. Every number is Martin's own statement on air and several are given as ranges or approximations in his own words: "a nice reliable eight-figure run rate," "I think we should be floating around 25 growth this year," "I think we did like 195 growth" for 2020, "about 43 different countries," "like 200 people in our organization." No dashboard, filing or third-party dataset is shown at any point, and a run rate is an annualised snapshot rather than revenue collected. Pricing, customer count, churn, margins and funding history are never discussed. The 50%-thinner management layer and the employee net promoter scores of 72 versus an industry average of 36 come from Martin's own research for his book, describing asynchronous companies he interviewed — they are not Time Doctor's audited figures, and the book is a commercial product he is promoting in this episode. The retreat cost of half a million to a million dollars per event is his figure for his own company. No country or city for the company or the founder appears in the transcript, so none is recorded here; the group file's "Brazil / Portuguese" labels are search-query tags, not evidence — the episode is in English. ProvenStartups has not verified any of it and makes no claim about the company after 2022.
The revenue unit for this category is a seat per month, and the first payment comes from a small team rather than an enterprise.
Two engines are visible. The first was exogenous and enormous: in 2020 every company on earth went remote at once, the category expanded overnight, and Time Doctor grew about 195% in a single year.
For a twelve-year-old SaaS the quiet stretches are not at the start, they are the eighteen-month experiments whose payoff nobody can measure, and Martin is unusually honest about running those.
Time Doctor is time-tracking software for distributed teams — Walling introduces it as a SaaS app for time tracking and Martin does not elaborate on the feature set in this episode, so treat the product description here as thin on purpose. What matters for anyone studying it is the shape of the category. Time tracking is a per-seat subscription with a buyer (the manager) who is different from the user (the worker), which produces an unusual set of product constraints: the thing has to be accurate enough to settle a payment dispute, light enough that the workforce does not revolt, and trustworthy enough on privacy that a company will install it on machines it does not own. Our read: the product is a commodity and everyone in this market knows it. There are dozens of time trackers, the core feature set has been stable for a decade, and no buyer switches for a better timer. What differentiates at this scale is integration depth (payroll, project management, invoicing), reporting a finance team will accept, and distribution. That is why Martin's real asset is not the software — it is being the person who wrote the book on how distributed companies operate, and therefore the default name when a company that has just gone remote goes looking. If you take one product lesson from this file, take that one: in a commodity category the moat is the reason people have heard of you, and it has to be built somewhere other than the product roadmap.
Per-seat subscriptions, sold to companies with distributed workforces, at a scale the founder describes only as "a nice reliable eight-figure run rate" growing around 25% a year. Our read: no pricing, ARPU, churn, gross margin or customer count is disclosed anywhere in this interview, so the eight-figure figure is the only revenue data point and it is a range, not a number. Two structural economics are visible anyway. First, expansion is built in: the customer is a team, teams grow, and seats grow with them, which is why 25% annual growth is achievable on a mature base in a commodity category. Second, and more interesting, is the cost side. Martin's research finding — that asynchronous organisations run a management layer 50% thinner than their on-premise counterparts — is a margin claim as much as a culture claim. "There are more people doing work in async orgs than there are people managing people solving problems inside of asynchronous orgs, and that is a massive strategic advantage when you're thinking about growing a company." The offsetting cost is deliberate and large: one company-wide retreat and one departmental retreat a year, which he says runs between half a million and a million dollars per event, justified by a measurable bump in employee net promoter score rather than by any revenue attribution.
This is the part worth stealing, and it is specific. Silent meetings: issues go into Asana before the meeting, everyone responds in the comments, and when a thread reaches a conclusion it gets moved to the top of the ticket and the ticket is cleared. If fewer than three tickets remain within 24 hours of the scheduled time, the meeting auto-cancels on everyone's Google Calendar — and Martin says you can watch people race to clear tickets the day before precisely so the meeting dies. Engineering is run on flow state rather than on a schedule: no nine-to-five shape, everything at the developer's disposal, and "let us know when it's done." He compares it to how creative writers work, disappearing for three or four days and re-emerging. Synchronous time is rationed on an explicit principle: an office company pays its collaboration cost once, in the commute, and then treats the day as a buffet, while a distributed company pays it every single time, so the question is always the minimum effective dose. The one thing he insists must stay synchronous is emotional conflict — the tickets that never clear are the interpersonal ones, and that is where managers should spend their energy, because the platform already handles the metrics. Retreats run at one company-wide and one departmental per year, six months apart, in three cities, chosen partly for being hard to get to. Our read: the auto-cancelling meeting rule is the single highest-leverage thing in this episode for a team of any size, because it converts a norm everybody agrees with in principle into a default that enforces itself.
Copy the operating model, not the product. A two-to-twenty person company can adopt the whole async stack this week at zero cost: write the meeting agenda as tickets, resolve what can be resolved in comments, auto-cancel when the queue is thin, protect maker time in multi-day blocks, and reserve live conversation for disagreement and emotion. If you hire, take the hiring implication seriously as well — Martin says psychometric testing shows introversion is one of the best predictors of long retention in remote organisations, which is an uncomfortable finding but a cheap one to act on. Take the retreat cadence too, and take the correction with it: Walling ran quarterly retreats for his remote accelerator and the founders told him it was too often; roughly every six months is where both of them landed. Change the category. Time tracking in 2026 is commoditised, contested, and carries a reputational problem the interview never touches. Our read: if you want per-seat revenue from distributed teams, the openings are in the adjacent jobs that time tracking only implies — contractor payment reconciliation across borders, async status and decision logging, or the compliance paperwork that follows hiring in 43 countries. Those are the problems a company running Martin's model actually has, and almost none of them have a default tool yet.
First, note the vintage and the source: this is an August 2022 podcast, every figure is Martin's own statement, and this entry makes no claim about what the business has done since. On the business itself, the largest risk is the one the interview never raises. Our read: employee monitoring is a politically exposed product. It sits inside workplace privacy law that varies by country and keeps tightening, it depends on installing software on machines the buyer may not own, and it is the category most likely to be legislated or culturally rejected — for a company with staff in 43 countries, that is 43 regulatory surfaces, not one. Second, category commoditisation: dozens of comparable trackers, a stable feature set, and payroll and project-management suites bundling time tracking into products companies already pay for. Third, demand pull-forward. A year of roughly 195% growth in 2020 borrowed from the future, and the numbers here — around 25% — are the post-shock reality. Fourth, execution risk inside the async model itself: Martin concedes the flow-state engineering approach is an eighteen-month experiment with no metric he trusts, and that nobody has produced a dataset justifying seven-figure retreat spending. Both are defensible bets, but they are bets. Fifth, key-person concentration: the authority asset is one co-founder's book, research and speaking, which does not transfer with a share certificate.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,435 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click