You've just landed the proposal leader role. Now comes the part no one fully prepares you for: figuring out what to fix first, who to talk to, and how to build credibility before your first big bid deadline hits.
This guide walks through each phase of your first 90 days—from auditing your content infrastructure to delivering quick wins and presenting a roadmap that earns executive buy-in.
Why the first 90 days matter for a new proposal leader
Your first 90 days as a proposal leader require a strategic balance between listening, assessing workflows, and driving momentum. The way you show up in the first few months shapes how BD teams, delivery leads, and executives perceive you—and with 27 to 46 percent of leadership transitions regarded as failures, the stakes are high.
Here's the thing most new proposal leaders don't realize until they're in the thick of it: you're not just inheriting processes. You're inheriting data. The quality of your firm's resume and project credential information determines what's actually possible when a bid lands on your desk. If that data lives in scattered folders, outdated spreadsheets, and email attachments, even the best process improvements will hit a ceiling fast.
What a 30 60 90 day plan looks like for proposal leadership
The 30-60-90 framework breaks your onboarding into three phases: learning, contributing, and leading. Each phase builds on the previous one, which keeps you from making changes before you understand the landscape.
This structure protects you from the most common onboarding failure: making changes before understanding why they exist in the first place.
How to prepare before day one
If you can get access to materials before your start date, use that time. Even a few hours of preparation accelerates trust-building in your first week.
Review recent wins and losses
Ask for debrief notes or post-mortems from the past six to twelve months. Look for patterns in why bids succeeded or failed—content quality issues, timeline crunches, or team availability problems. The patterns tell you where to focus your attention.
Get familiar with the active bid pipeline
Find out what pursuits are already in flight. If there's a major deadline in your first two weeks, you'll want to contribute rather than sit on the sidelines observing.
Map the existing proposal tech stack
List the tools currently in use: CRM, document storage, proposal software, and anything else the team touches regularly. Note gaps, especially around how resumes and project credentials are managed. This is often where the biggest inefficiencies hide.
How to audit your proposal function in the first two weeks
Think of this audit as a diagnostic, not a judgment. You're documenting where the function is strong and where data or process gaps slow the team down.
People and team capacity
Who owns what in the bid process? Are proposal managers stretched across too many pursuits at once? Document roles and bandwidth honestly—this becomes your baseline for any future recommendations.
Process and workflow
Map the typical bid lifecycle from opportunity identification to submission. Where do things stall? Common bottlenecks include content collection, approvals, and last-minute formatting scrambles.
Content library resumes and project credentials
This is often the biggest gap. When assessing your content library, look at whether resumes and project sheets are:
- Centralized: Stored in one searchable place, or scattered across shared drives and email attachments
- Current: Regularly updated by employees, or stale and unreliable
- Tailored: Easy to customize for different bid types, or static one-size-fits-all documents
Platforms like Flowcase give proposal teams a single source of truth for resume and project data, which makes auditing and improving content much faster. When everything lives in one structured, searchable system, you can actually see what you're working with.
Tools and integrations
Evaluate whether existing tools talk to each other. The best proposal software integrates with systems like Salesforce, Workday, or PSA tools the firm already uses—so data flows without manual re-entry.
Key stakeholders every proposal leader should meet early
Relationship-building is the foundation of influence in this role. Use your first weeks to listen more than prescribe.
Business development and capture leads
Understand how opportunities are qualified and prioritized. Learn their frustrations with current proposal support—this tells you what they'll value most from you.
Subject matter experts and technical leads
SMEs write or inform technical content. Learn how they prefer to be engaged on bids. Some want early involvement; others prefer to review drafts near the end.
Marketing and brand
Clarify ownership of templates, messaging, and visual standards. Identify overlaps or gaps in responsibilities so you're not stepping on toes later.
Delivery and operations
Delivery teams know which projects went well and which staff are available. Build a channel for sourcing project credentials—they're often your best source of recent, relevant experience.
Executive sponsors and partners
Understand their expectations for win rate, bid volume, and strategic pursuits. Clarify how they want to be involved in major bids.
Questions to ask during your listening tour
Open-ended questions surface pain points and perceptions you won't find in documentation:
- What's working well in how we pursue and win work?
- Where do bids typically stall or fall apart?
- How easy is it to find the right resumes and project examples for a pursuit?
- What would make contributing to proposals easier for you?
- If you could fix one thing about our bid process, what would it be?
Days 1 to 30: learn the function and build trust
The first month is for observation and documentation. Resist the urge to change things before you understand them.
1. Complete your function audit
Finalize your assessment of people, process, content, and tools. Write a brief internal document summarizing findings—this becomes your reference point for everything that follows.
2. Build relationships with bid contributors
Meet individually with frequent contributors. Learn their preferred working style and past frustrations. The conversations pay dividends when you need their help later.
3. Document the current state honestly
Create a simple reference showing how bids currently flow, where content lives, and who approves what. Share with your manager for alignment.
Days 31 to 60: deliver quick wins and tighten the process
Now that you understand the function, take visible action. Quick wins build credibility and momentum with the broader team.
1. Standardize resumes and project sheets
Create or improve templates for resumes and project credentials.
If resume data is scattered across drives and inboxes, consider consolidating it into a centralized platform.
Tools like Flowcase allow teams to maintain structured, searchable resume and project data that can be tailored quickly for each bid—without hunting through folders or asking colleagues to send updated versions.
2. Improve a live bid in flight
Pick one active pursuit and improve it: better tailoring, cleaner formatting, stronger win themes. Make the improvement visible to stakeholders so they see the value you're adding.
3. Establish a bid review cadence
Introduce a recurring checkpoint—kick-off, draft review, final review—for active pursuits. Keep it lightweight to encourage adoption.
Days 61 to 90: lead the strategy and set the roadmap
By now you have credibility. Transition from fixing immediate issues to shaping the function's future direction.
1. Present a twelve month proposal roadmap
Outline priorities for the next year: process improvements, tool investments, team development. Tie recommendations to business goals like win rate or bid capacity.
2. Make the case for better tools and data
If the audit revealed gaps in resume or project credential management, build a business case for addressing them. Emphasize the value of clean, structured, searchable data that integrates with existing systems.
Flowcase is purpose-built for this—centralizing CVs and project experience so bid teams can find, tailor, and reuse content without manual hunting. Unlike tools that rely on static document storage, Flowcase maintains structured data that works with any AI tool or integration your firm adopts.
3. Align hiring and capacity plans
Based on projected bid volume, recommend whether the team needs additional headcount, contractor support, or better tools to scale without adding staff.
Proposal KPIs to track from day one
You need baseline metrics to measure progress. Start tracking early, even if data is imperfect.
- Win rate by pursuit type: Segment by bid type (competitive RFP, sole-source, recompete). Different pursuit types have different benchmarks, though the average RFP win rate is 45%.
- Proposal cycle time: Measure how long bids take from kick-off to submission. Identify where delays typically occur.
- Response capacity and bid volume: Track how many bids the team can realistically support at once. Note when capacity constraints force no-bid decisions.
- Content reuse and tailoring ratio: Assess how much content is reused versus written from scratch. High reuse with smart tailoring signals efficiency.
Common pitfalls new proposal leaders avoid
Experienced proposal leaders often see the same mistakes repeated. Here's what to watch for.
Rebuilding processes before diagnosing them
Changing workflows before understanding why they exist creates friction with the team. Listen first, then improve.
Ignoring the state of resume and project data
Many proposal problems trace back to poor content infrastructure. If resumes and project credentials are outdated or scattered, even great processes will struggle to deliver results.
Chasing volume over win quality
Submitting more bids is not always better. Focus on pursuits where the firm has a credible path to win.
Skipping alignment with BD and delivery
Proposal leaders who operate in isolation lose influence over time. Stay connected to upstream (BD) and downstream (delivery) stakeholders.
Setting your proposal team up to scale beyond day 90
The first 90 days are foundational, but sustained success requires ongoing investment in people, process, and content infrastructure.
Firms using platforms like Flowcase can scale bid capacity without proportionally adding headcount because structured data and automation reduce repetitive work. When your resume and project data is clean and searchable, your team spends time on strategy and story—not on hunting for content.
Book a demo to see how Flowcase supports proposal teams.
Frequently asked questions about your first 90 days as a proposal leader
What should a leader do in the first 90 days?
A new leader focuses on learning the organization, building key relationships, diagnosing the current state, and delivering a few visible wins before proposing major changes.
What is the 30 60 90 rule in leadership?
The 30-60-90 framework divides onboarding into three phases: learning (days 1-30), contributing (days 31-60), and leading (days 61-90) to ensure steady progress without rushing decisions.
How is proposal leadership different from general management?
Proposal leaders manage cross-functional contributors who don't report to them, requiring influence and coordination skills rather than direct authority over a fixed team.
When is the right time to start changing tools or processes?
Wait until you've completed a thorough audit and built relationships—typically after the first 30 days—before recommending significant tool or process changes.
.png)