The most common complaint founders make about time tracking is that it doesn’t tell them anything useful. They log their hours, look at a pie chart, and feel vaguely informed but not actually helped.
The problem is usually the categories. If you track time against project names or task types, you get data that’s too granular to reveal strategic patterns and too specific to suggest strategic changes. You can see that you spent 12 hours in “customer meetings” this week. You can’t see whether that’s the right amount for your current stage — or whether those 12 hours displaced something more critical.
The Founder Time Triangle solves this by using three categories that map to the three fundamental activities of a startup: creating the thing (Build), selling the thing (Sell), and keeping the organization running (Operate). At each stage of company growth, there’s a rough target ratio between these three — and the gap between your actual ratio and your target ratio is the most actionable signal in founder productivity.
Why These Three Categories
Every task a founder does is fundamentally one of three things.
Build is value creation at the product level. It’s the activity that makes the thing better. Engineering, product design, UX decisions, technical architecture, prototype work, product strategy — if the output is a better product or a clearer product roadmap, it’s Build.
Sell is value capture. It’s the activity that converts the product’s value into revenue, users, or the investment that makes future revenue possible. Sales calls, demo presentations, proposal writing, fundraising, investor relations, marketing strategy, content that drives acquisition, partnership negotiation — if the output is money in or the pipeline that leads to money in, it’s Sell.
Operate is organizational sustenance. It’s the work that keeps the company able to function. Hiring, HR, legal, finance, accounting, compliance, office management, internal processes, and management of people who aren’t doing Build or Sell work. If the output is an organization that can keep going, it’s Operate.
These three categories are exhaustive — every founder task fits somewhere — and they’re coarse enough to categorize without deliberation. Most tasks are instantly recognizable as one of the three.
The Target Ratios by Stage
The right mix depends entirely on what your company needs right now. Here’s how the triangle typically should look at each stage:
Pre-seed / Idea stage: 60% Build, 30% Sell, 10% Operate
You’re testing whether the thing is worth building. Most of your time should be creation and customer discovery. Paul Graham’s “do things that don’t scale” advice is essentially a recommendation to be in Build and Sell almost exclusively. Operate tasks at this stage are largely avoidable — don’t form entities before you need to, don’t hire before you must.
Seed stage: 50% Build, 30% Sell, 20% Operate
You’ve raised money and have product direction. Build remains dominant because product-market fit isn’t certain yet. Sell is significant because you need customers or users to validate the direction. Operate increases because you now have a real company — payroll, contracts, early hires.
Series A: 30% Build, 40% Sell, 30% Operate
The transition point. By Series A, the product works. The question is whether it scales commercially. Sell becomes the dominant category because growth is the primary goal. Operate grows because the organization is larger. Build shrinks as a founder priority because you now have engineering and product people who own it.
Series B and beyond: 20% Build, 30% Sell, 50% Operate
The founder is now primarily an organizational leader. Most of the building and much of the selling is done by other people. Operate dominates because the founder’s highest-leverage work is building the team, culture, and process that executes at scale.
These are empirical targets, not prescriptions. They come from studying how successful founders actually spend their time at each stage, cross-referenced with First Round Review’s founder productivity research and the patterns documented in Paul Graham’s writing on early-stage company building.
How AI Adds the Variance Layer
Historical time tracking tools gave you descriptive data: here’s how you spent your time. The insight layer — what this means, whether it’s right, what to do about it — was left to the founder.
AI changes this by providing interpretation on demand.
Weekly variance detection is the most immediate value. After logging your week’s categories, you paste them to an AI and ask it to calculate your actual ratio against your target. A seed-stage founder who spent 35% Build, 20% Sell, and 45% Operate in a given week is 15 points below Build target and 25 points above Operate target. That’s a significant deviation — and without the calculation, it might not be obvious from the raw log.
Multi-week trend analysis is where AI earns its keep. A single Operate-heavy week might be explained by a necessary hiring sprint. Three Operate-heavy weeks in a row is a structural problem. AI can process four weeks of logs simultaneously and flag the trend — something that would require careful manual tabulation to detect otherwise.
Pattern attribution goes beyond just identifying the deviation: it helps explain it. An AI conversation about a month of logs can identify that Operate spikes consistently happen on weeks with multiple new-hire onboarding, or that Build time is systematically lower in weeks that start with all-hands meetings on Monday morning.
Beyond Time automates this variance layer. You log your daily categories (the habit); the platform calculates your weekly ratio, compares it to your target, and surfaces any multi-week drift without requiring you to manually run the analysis each time.
The logic is the same whether you use a dedicated tool or a general-purpose AI. The difference is friction. A tool that does the analysis automatically removes the step that’s most likely to be skipped on a busy Friday.
Using the Framework to Make Decisions
The power of the Founder Time Triangle isn’t in the data — it’s in the decisions the data enables.
Hiring decisions. If your Operate percentage has been above 35% for three consecutive months at the seed stage, you have a structural argument for your next hire. Not a “we need someone to help out” argument — a data argument. “Operations work is consuming 35% of my time, well above the 20% target. An ops or finance hire would reclaim 10-15% of my weekly hours for Build and Sell.” Investors understand this framing.
Delegation decisions. Looking at what specifically is driving your Operate hours often reveals tasks that are lower-leverage than they appear. Contract review, calendar management, vendor relationships — these often feel founder-critical but aren’t. The triangle data makes the opportunity cost concrete.
Calendar design. If your Build hours are consistently lower than your target, the question becomes: when during the week does Build work get scheduled, and what displaces it? AI analysis of your logs often reveals that Build time is highest on certain days and nearly absent on others — a pattern you can design around.
Fundraising timing. Sell hours typically spike during a fundraising process. This is expected and unavoidable. But tracking it makes the cost visible. If a raise is consuming 50% of your time for three months, you have concrete data about the organizational cost — and a basis for planning what you’ll need the team to cover.
The Sub-Triangle: When You Need More Granularity
The three-bucket model works for most founders most of the time. But sometimes you need more detail within a category.
A common example: a founder whose Sell numbers look right but revenue growth is flat. The issue is often the composition of Sell hours — high ratio of pipeline admin and marketing tasks, low ratio of direct customer conversations and closing activity.
In this case, you can add one level of sub-categorization to Sell:
- Sell-High: Direct customer contact (calls, demos, negotiations, success calls)
- Sell-Low: Indirect activities (email templates, pitch deck polish, CRM updates, marketing campaigns)
The same logic applies to Build (Sell-High = customer-facing features, Sell-Low = tech debt cleanup) and Operate (Operate-High = hiring, Operate-Low = admin tasks that could be outsourced).
The sub-triangle is optional and should only be added when the three-bucket model is working smoothly and you have a specific question the basic data isn’t answering.
Interpreting the Triangle Across Time
The ratios should change as your company evolves. If you track consistently for 12 months, you should be able to see the natural evolution of your triangle — the gradual shift from Build-heavy to Sell-heavy to Operate-heavy as the company matures.
If your ratios haven’t changed significantly in 12 months despite significant growth, that’s a signal worth investigating. It usually means one of two things: either your role hasn’t evolved with the company (a common founder trap), or the organization hasn’t developed enough for you to delegate effectively.
Both of these are important to know. Neither is visible without tracking.
Pair the triangle data with your company milestones. When did you find product-market fit? When did you close your seed round? When did you hire your first sales rep? Layering these events onto your ratio history often reveals inflection points — and sometimes reveals that your time allocation didn’t shift when it should have.
The Framework as a Shared Tool
For cofounders, the triangle has an additional use: alignment.
Two founders who track their time using the same framework can compare their triangles and have a concrete conversation about division of labor. If both are spending 40% on Operate, something is wrong — or something structural needs to change. If one is all-Build and the other is all-Sell, the question is whether that’s intentional or whether the Operate work is falling through the cracks.
A monthly cofounder review using the triangle data is a significantly more grounded conversation than “how do you feel about your workload” — and it surfaces misalignment before it becomes resentment.
Starting Point: Calculate Your Baseline This Week
Before worrying about targets and ratios, find out where you actually are.
This week, at the end of each day, write one word: Build, Sell, or Operate. Do this for five days. On Friday, count them up and estimate your rough ratio.
Then ask yourself: is this what the company needs right now?
That one question — honestly answered — is worth more than any sophisticated tracking system. The framework just gives you the vocabulary to answer it with data instead of instinct.
For the next step — how to set up the daily habit and run the weekly AI review — the practical how-to guide walks through the logistics in detail.
Frequently Asked Questions
-
Why three categories and not more?
Three categories is the right granularity for a daily logging habit that survives chaos. More categories add precision but also friction — and most founders don't need to distinguish between, say, marketing and sales at the category level for their first pass at time awareness. The three-bucket model answers the most important question — are you building, selling, or operating? — with minimal cognitive overhead. You can add sub-categories later once the habit is established.
-
What if I genuinely can't tell which category a task belongs in?
When in doubt, ask: does this task create value (Build/Sell) or sustain it (Operate)? Hiring is Operate — it sustains the organization. A sales call is Sell — it creates revenue. Product design is Build — it creates value. When tasks span categories (e.g., a founder-led customer interview that informs product direction), assign it to the primary purpose or split it. The exact assignment matters less than consistency.
-
How does the target ratio change as the company grows?
In the pre-seed and early seed stage, Build should dominate — you're creating the thing. As you approach and find product-market fit, Sell increases as converting and retaining customers becomes critical. From Series A onward, Operate grows substantially as the founder's role shifts toward building the organization rather than building the product. The shift from maker to manager — Paul Graham's framing — is visible in the triangle's ratios changing over time.