Path From BA to Senior BA and BI Lead

You're two or three years in. You ship six to eight dashboards a quarter. You close forty-something ad-hoc tickets a month. Your manager keeps saying "great work" in 1:1s and the comp review keeps landing you another 4% bump on $95K. The Senior BA role opened twice this year and went to outside hires both times. Nobody told you why.

I'll tell you why. You're a report-builder, and the org figured it out before you did.

Senior BA isn't "more dashboards faster." BI Lead isn't "more reports for the C-suite." Both are different jobs from what you're doing right now. Most BAs never figure out the switch in time. They keep optimizing for ticket throughput, plateau at $115K, and watch a Senior BA hire come in from outside on $140K.

This is the playbook for not being that person.

The Report-Builder Trap

Here's the thing nobody says out loud: ticket-close rate is the worst possible signal for promotion above mid-level.

The org rewards visible output at the IC tier because it's easy to measure. Forty tickets closed, twelve dashboards shipped, two SQL audits done. Great. That gets you to mid-BA. Every level above mid-BA, though, is measured on leverage. Decisions enabled per analyst. Hours of exec time saved. Initiatives unblocked across teams. Not queries closed per week.

Senior BAs who came up purely on volume hit a ceiling because the next role isn't "do this faster." It's "stop doing this and run the people who do." If you're still pulling 40 tickets a month at year four, you're not a Senior BA candidate. You're a fast IC, and the company will keep treating you like one because that's what you've optimized for.

The trap closes quietly. You feel productive. Slack pings reward you. Your manager has nothing to complain about. And the title sits there for another year.

What Changes at Senior BA: 12 to 18 Months Out

Senior BA is the first role where output stops being the point. Three things actually change.

You own a domain end-to-end. Pick one: revenue, retention, or product analytics. You become the canonical source. Every disagreement on the number ends with you. When the CRO and the CFO have different revenue figures, the fix is your model, not a meeting. When product wants retention by cohort and finance wants it by ARR band, you own which one is "correct" and you defend it. This is not "I work mostly on revenue dashboards." It's "if a number about revenue is wrong, it's my fault, and if it's right, it's because I built the system that makes it right."

You mentor one IC BA. Formal or informal, doesn't matter. Code-review their SQL. Sit in their stakeholder meetings and let them run it. Give them the hard ad-hoc that you would've taken yourself eighteen months ago. Their growth is now a measure of yours. If they're still writing window functions wrong six months in, your manager notices. If they're presenting to the VP of Sales by month four, your manager notices that too.

You run intake. You triage. You scope. You reject. You are the first "no" so the team can ship. This is the one most ICs hate, because saying "no" to a stakeholder feels like getting fired in slow motion. It's not. The senior people who can't say no are the ones who get fired in slow motion, because their teams quit.

The flip side: stop being the on-call dashboard fixer. Delegate. If you can't, the gap is staffing or process, not your throughput. Make that argument to your manager with a model: incoming volume, current capacity, time-to-resolution. You're not whining; you're sizing the gap.

Comp band: $110-145K base. Bonus 10-15%. Some equity at Series B (~0.02-0.05%, real money only on a good exit). Series B SaaS lands around $120K. Public co. lands $135-145K. NYC and SF run 15-25% higher. Atlanta and Austin run 10-20% lower. Remote-only roles tend to anchor to the lower end of that band unless you're already at a top-tier name.

What Changes at BI Lead: 24 to 36 Months Out

BI Lead is a different job again. Don't confuse it with "Senior BA but more so."

You own the analytics roadmap. Not dashboards. Not tickets. The roadmap. You decide what the team builds next quarter, and you defend it against four directors who all want their thing first. You write a quarterly OKR for the analytics team and you publish it. You retire dashboards on purpose, not because they broke. You sunset metrics that nobody uses. You name the things the team is not going to do, in writing, so the team can ship the things it is doing.

You manage two to four ICs. This means 1:1s every week, performance reviews twice a year, hiring loops, ramps, comp conversations, sometimes a PIP. Roughly 30-40% of your week is people work, not SQL. Most BAs underestimate how much of this is emotional labor. You're going to have a 1:1 where someone cries. You're going to have to tell a senior IC their comp is below market and you can't fix it this cycle. You're going to debrief a panel after rejecting a candidate the team liked. None of this shows up in a dashboard.

You defend headcount and tooling to the CFO. This is the capability nobody trains you for, and it kills more first-time BI Leads than any technical gap. You walk into a budget review, and the CFO asks why the analytics tooling line item is $52,000 a year. You have ten minutes. You need a model: incoming request volume, average time-to-insight today, target time-to-insight next year, capacity gap, what each tool unlocks against the gap. Not "Looker is industry standard." Not "the team likes Hex." A capacity argument tied to a business outcome, with numbers you'd stake your job on. Same for the next hire. You don't get to ask. You build the case and present it like a PM presenting a feature.

You set the metric layer strategy. dbt versus a vendor semantic layer. Governance: who can publish a model, who can change a definition, how breaking changes get communicated. Data contracts with engineering. SLAs on freshness. This is architecture work, not analysis work, and it's what separates BI Lead from "Senior BA who got promoted to manager." If you don't have an opinion on metric governance by the time you interview for the role, you're not ready.

Comp band: $145-190K base. Bonus 15-20%. Equity 0.05-0.15%. BI Lead at a 200-person SaaS lands around $160K. Director-of-Analytics-track at a public co. lands $180-190K base, plus meaningful RSUs ($40-80K/year vesting on a four-year cliff at a stable public name). The total comp gap between Senior BA and BI Lead is real, usually $50-70K all-in. It's not a bigger title with a 5% bump.

The Four Capabilities You Have to Build

If you don't build these, you don't get there. Pick them off one a quarter.

1. Data modeling at scale. dbt. Semantic layers. Slowly-changing dimensions. Lineage. Governance. Stop writing one-off CTEs for stakeholders. Start owning the canonical models other people query. The shift is from "here's the SQL that answers your question" to "here's the model anyone in finance can query to answer this class of question forever." If your company doesn't run dbt, learn it on the side. You'll inherit the migration sooner than you think.

2. Exec storytelling. A three-slide deck that survives a fifteen-minute exec review. The ability to walk a CFO through a retention curve and have them leave with one decision, not five questions. This is a learned skill, and it's not the same as "making a good chart." It's structure: the question, the answer, the implication, the ask. Practice it in front of your manager before you need it for a board prep. Volunteer to present a board-prep slide once a quarter even if it's terrifying. The first three times will be bad. The fifth time will be the reason you get the BI Lead role.

3. Hiring. Run a take-home. Debrief a panel without dominating it. Write a leveling rubric: Senior versus Staff versus Lead, with concrete behaviors at each level. Most BAs have never written a job spec. Volunteer to draft the next BA req. Sit in a phone screen. Read fifty resumes for one role and tell me what you'd reject for. Hiring is the highest-leverage skill at the BI Lead tier. One bad hire costs you a year. One great hire makes your year.

4. Vendor management. Negotiate a Looker, Hex, or dbt Cloud renewal. Sit through a procurement cycle. Know what 20% off list price looks like and what tradeoffs come with it (longer contract, prepay, a case study, an integration commitment). Know which vendors will throw in pro services to close, and which won't. Sit next to your manager during the next renewal and watch how the call goes. Then ask to lead the one after that.

The Comp Ladder, Real Numbers

USD, US-based, B2B SaaS Series B through public, 2026. Adjust for geography.

NYC and SF run 15-25% higher. Austin and Atlanta run 10-20% lower. Outside the US, expect 30-40% lower in most markets, with the gap closing in London, Berlin, and Sydney for senior roles. Public co. comp is heavier on RSUs and lower on bonus. Late-stage privates trend to higher base and weaker equity than the cap table suggests.

If your current company won't pay these numbers at the next promotion, leave for one that will. Internal promos historically lag external offers by 10-15% even at well-run companies. That gap is not your imagination.

The 18-Month Plan

Twelve months is too tight. Twenty-four is too loose. Eighteen is the window where most internal promos actually clear.

Months 1-6: Pick a domain, become the canonical owner. Pick revenue, retention, or product. Map every dashboard, model, and metric in that domain. Find the contradictions and resolve them, in writing, with stakeholder sign-off. By month six, when there's a disagreement on the number, your name is the resolution.

Months 7-12: Mentor an IC, own intake, ship one cross-team initiative. Ask your manager for a junior to mentor. Take over intake triage for the team. Pick one initiative that crosses two teams (revenue + product, retention + support) and run it end-to-end as the analytics owner.

Months 13-18: Make the Senior BA case in writing, get the title, then start the BI Lead conversation about the next 18 months. Write a brag doc. Three pages, max. Domain ownership, mentee progress, intake metrics, the cross-team initiative. Bring it to your manager four months before the cycle. Don't ask if you should be promoted — present the case and ask what's missing.

A brag doc isn't bragging. It's the artifact your manager needs to fight for you in a calibration meeting where they have eight minutes and ten people to defend. Make their job easy.

The "I Don't Want to Manage People" Exit

Management isn't the only path. The parallel ladder is Staff Analyst then Principal Analyst: IC depth instead of breadth. Comp lands similar to BI Lead, sometimes a touch lower at the Staff tier and similar at Principal.

The work stays technical. You own the hardest models, the most ambiguous problems, the ones nobody else can solve. You don't run 1:1s. You don't sit in calibration meetings. You don't fight the CFO over headcount. You write the dbt models that everyone else queries, and you write the docs that explain why.

One catch. Most companies say this ladder exists. Roughly 30% actually fund it, meaning they actually promote people to Staff and Principal Analyst, with comp that matches the management track, on a regular cycle. The other 70% have it on a slide somewhere and last promoted someone to Staff in 2022. Verify before you bet your career on it. Ask your skip-level: "How many Staff Analysts do we have, and when was the last Principal Analyst promotion?" If the answer is "we'd have to check," you have your answer.

Common Traps

The patterns that kill BA careers, in rough order of frequency:

• Optimizing for ticket-close rate past mid-BA.
• Refusing to delegate because "it's faster if I just do it." It's faster this week. It's slower this year.
• Never writing things down. No brag doc, no design doc, no decision log. If it's not written, it didn't happen at promo time.
• Waiting to be told you're ready. Nobody is going to walk into your 1:1 and announce it. You raise the conversation.
• Ignoring the people side until the day you're offered the role. You can't learn to manage in the first month of managing. Practice mentoring now.
• Never presenting to execs until forced. The first exec presentation should not be the board.
• Letting your tools atrophy. If you haven't shipped a dbt model in six months and the rest of the industry has, you're falling behind quietly.

The Closing

The promotion isn't a reward for shipping more dashboards. It's a bet that you can run the function. The company is asking: can this person own a domain, develop people, defend a budget, and set strategy? Most of the work that earns the bet happens 12-18 months before the title shows up.

Start acting like the role you want. Pick the domain. Take the mentee. Run intake. Write the brag doc. Have the conversation. The title follows.

If it doesn't follow at your current company within 18 months of doing all four — leave. The market will pay you for the work even if your manager won't.

Learn More

• Business Analyst Job Description Template
• Your First 30/60/90 Days as a New Business Analyst
• Stakeholder Management Without Becoming the Help Desk
• BA Metrics: Time-to-Insight, Decision Impact, NPS