Subcontractor Documentation - A Workforce Flexibility Indicator for M&A Readiness

How systematic subcontractor documentation can reveal workforce flexibility and classification compliance that buyers often evaluate during acquisition diligence

20 min read Exit Strategy, Planning, and Readiness

The stack of subcontractor agreements sitting in your filing cabinet may tell sophisticated buyers more about your operational discipline than almost any other document set they’ll review. These aren’t just legal formalities but windows into how you approach workforce flexibility, regulatory compliance, and scalable operations. Yet in our experience working with business owners preparing for exit, subcontractor documentation consistently ranks among the most underestimated areas of due diligence preparation, particularly in industries with significant subcontractor usage such as technology, professional services, and construction.

Executive Summary

Subcontractor relationships represent one of the most scrutinized areas during M&A due diligence, yet most business owners underestimate how their documentation practices may affect buyer perception and deal terms. When buyers evaluate companies in what we define as the $2M-$20M revenue range (a segment we focus on because these businesses often lack dedicated HR and legal functions yet face similar compliance scrutiny as larger enterprises), they’re typically not just looking at whether you use subcontractors. They’re often assessing whether your documentation demonstrates the operational discipline and compliance attention that may reduce post-acquisition risk.

Critical caveat before proceeding: Systematic documentation alone cannot protect against misclassification liability. If underlying relationships don’t genuinely qualify as independent contractor arrangements, no amount of documentation will provide legal protection. In fact, comprehensive documentation of employment-like relationships can create evidence that worsens your exposure. This article addresses documentation for legitimate contractor relationships, not how to paper over problematic ones.

Disorganized stack of business documents and papers scattered across wooden desk surface

This analysis examines subcontractor documentation standards that experienced acquirers may apply during operational and employment diligence. We look at how subcontractor program sophistication often correlates with buyer assessments of operational flexibility, why systematic documentation practices may signal broader organizational capability, and what specific documentation frameworks can demonstrate both compliance discipline and scalable operations.

For business owners planning exits within the next two to seven years (the horizon we typically see for meaningful exit preparation based on our client work), understanding these documentation expectations provides actionable guidance for building subcontractor programs that may reduce transaction friction. But the actual impact on enterprise value varies significantly based on buyer priorities, deal structure, and your specific compliance risk profile. Documentation primarily reduces risk rather than directly creating value.

Introduction

Most business owners view subcontractor documentation through a narrow lens, primarily as legal protection against misclassification claims or IRS audits. While compliance certainly matters, this perspective often misses the broader strategic significance that subcontractor documentation may carry during M&A transactions.

Close-up of magnifying glass examining fine print text on legal contract document

In our experience, sophisticated buyers (particularly private equity firms and strategic acquirers with extensive M&A experience) often evaluate subcontractor documentation as one indicator of operational maturity. They may recognize that companies with disciplined subcontractor documentation often demonstrate similar discipline across other operational areas: vendor management, quality control, regulatory compliance, and process documentation. This correlation doesn’t prove causation; strong documentation reflects underlying operational discipline, but the discipline itself (not merely its documentation) drives operational excellence.

Conversely, weak subcontractor documentation may raise questions about broader organizational capabilities. If a company hasn’t systematically documented its most compliance-sensitive workforce relationships, buyers might reasonably wonder what other operational areas lack appropriate documentation and controls.

The subcontractor documentation challenge often intensifies for companies in our target revenue range. Unlike larger enterprises with dedicated HR and legal functions, businesses generating $2M-$20M in revenue typically manage subcontractor relationships through operational leaders who may lack specialized compliance training. This structural reality frequently creates documentation gaps that become visible (and potentially problematic) during buyer due diligence.

We’ve observed patterns in how buyers tend to evaluate subcontractor documentation and how documentation quality may affect deal outcomes. The difference between companies that navigate workforce due diligence smoothly and those that encounter significant friction often comes down to documentation practices that owners could have implemented years before contemplating a sale.

Modern flexible workspace with multiple laptops and digital collaboration tools setup

Important caveat: Documentation practices and their impact on transactions vary significantly by industry, geography, and buyer type. Some buyers weight documentation practices heavily while others focus primarily on financial performance. The guidance here represents patterns we’ve observed, not universal rules.

What Buyers Often Evaluate in Subcontractor Documentation

Understanding common buyer evaluation criteria helps business owners prioritize documentation improvements that may matter during due diligence. Experienced acquirers frequently apply systematic frameworks when reviewing subcontractor programs, looking beyond surface compliance to assess operational sophistication.

Classification Compliance Evidence

Row of colorful construction hard hats and safety equipment on industrial workbench

The threshold concern for most buyers involves misclassification risk. Under current IRS guidelines (see IRS Publication 15-A) and Department of Labor standards, reclassifying subcontractors as employees can trigger back taxes, penalties, benefits obligations, and potential litigation (liabilities that buyers typically inherit in most transaction structures). Consequently, buyers often scrutinize subcontractor documentation for evidence that supports independent contractor classification.

The IRS uses a multifactor test examining behavioral control, financial control, and relationship type. State-level tests vary considerably. California’s ABC test under AB5 applies stricter standards than many other states, while Texas generally follows federal guidelines more closely. This regulatory variation means documentation requirements differ meaningfully based on where your subcontractors work.

This evaluation goes beyond simply having contracts in place. Buyers often examine whether documentation reflects the economic reality of each relationship. They may look for scope definitions that describe deliverables rather than hours, payment terms based on project completion rather than time worked, and contract provisions that demonstrate genuine independence.

Documentation red flags often include contracts that specify working hours or locations, agreements that prohibit working for other clients, provisions requiring use of company equipment or systems, and terms suggesting ongoing employment-like relationships rather than project-based engagements. Even when the underlying relationship legitimately qualifies for independent contractor status, documentation that uses employment-like language can create due diligence friction.

Well-organized digital file management system displayed on computer screen with labeled folders

Critical warning: Documentation frameworks cannot protect against misclassification liability if underlying relationships don’t genuinely qualify as independent contractor arrangements. Contracts containing “magic language” about independence mean nothing if the day-to-day reality involves employment-like control. Buyers conducting thorough due diligence will interview subcontractors and examine operational practices, not just contract language. If your relationships don’t clearly meet contractor tests, consider converting them to employee status before implementing documentation frameworks. Attempting to document employment-like relationships as contractor arrangements may actually worsen your legal exposure by creating a paper trail of misrepresentation.

Operational Control Documentation

Beyond classification compliance, sophisticated buyers often evaluate subcontractor documentation for operational control indicators. They want to understand how you manage subcontractor quality, ensure deliverable standards, and maintain operational consistency without crossing into employment-like control.

Strong subcontractor documentation frameworks may demonstrate this balance through performance requirements that specify outcomes rather than methods, quality standards that define acceptable deliverables without dictating how subcontractors achieve them, and escalation procedures that address performance issues while respecting contractor independence.

Bright yellow caution tape blocking access to construction or restricted work area

Buyers particularly tend to value documentation that shows systematic approaches to subcontractor management: standardized contract templates, consistent onboarding processes, regular performance evaluation frameworks, and documented procedures for addressing quality concerns. This consistency may signal operational maturity that translates across other business functions.

But implementing outcome-based performance frameworks requires significant upfront investment in scope definition and may not be practical for all types of subcontractor work. Many relationships that work well operationally may not fit neatly into documentation frameworks that satisfy both compliance and operational control needs.

Contract Term Analysis

Experienced buyers typically analyze contract terms for indicators of genuine subcontractor relationships versus potentially disguised employment. They often examine termination provisions, exclusivity clauses, intellectual property assignments, confidentiality requirements, and liability allocations.

Financial calculator next to spreadsheet and budget planning documents on clean desk

Several contract elements frequently receive particular scrutiny. Automatic renewal provisions may suggest ongoing employment relationships rather than discrete project engagements. Exclusivity clauses restricting subcontractor ability to serve other clients can undermine independence arguments. Payment terms tied to hours rather than deliverables may raise classification questions.

Conversely, stronger contracts generally include clear project scope definitions with defined endpoints, payment structures tied to milestone completion, provisions acknowledging subcontractor independence and responsibility for their own taxes and benefits, and termination clauses that respect project-based relationship structures.

How Subcontractor Program Sophistication May Affect Flexibility Assessment

Buyers evaluating acquisition targets typically care about operational flexibility: the ability to scale resources up or down efficiently without proportional fixed cost changes. Subcontractor programs represent a primary flexibility mechanism, but buyers often assess whether your program actually delivers operational flexibility or primarily creates compliance exposure.

Detailed road map with planned route marked showing journey from start to destination

Scalability Indicators

Well-documented subcontractor programs may demonstrate scalability in ways that can reduce transaction friction. Buyers often look for evidence that you can efficiently onboard qualified subcontractors when demand increases and appropriately conclude relationships when projects complete. This typically requires standardized onboarding documentation, clear scope definition processes, and systematic offboarding procedures.

Companies that document subcontractor onboarding timelines, qualification verification processes, and performance evaluation frameworks often demonstrate the repeatable processes that may enable genuine scalability. While we cannot claim a direct causal relationship between documentation and valuation multiples, strong documentation practices often correlate with operational capabilities that buyers value.

The relationship between documentation and actual scalability is correlative, not necessarily causal. Documentation reflects underlying operational discipline, but the discipline itself (not merely its documentation) may drive scalable operations. Some companies with strong documentation still struggle operationally, while others with minimal documentation execute flawlessly.

Hand holding clipboard with completed checklist showing checked off business tasks and objectives

Dependency Risk Analysis

While subcontractor flexibility can boost value, subcontractor dependency may create concern. Buyers often evaluate documentation for concentration risk indicators: are critical capabilities dependent on specific subcontractors who might not continue post-acquisition?

Strong documentation may address dependency risk through qualification requirements that specify capability standards rather than individual contractors, backup subcontractor identification for critical functions, and knowledge transfer protocols that help prevent single-point-of-failure situations.

Documentation demonstrating multiple qualified subcontractors for key functions, systematic capability verification processes, and knowledge management practices that capture critical information regardless of individual contractors may signal operational resilience that buyers value.

Lone mountain climber standing at snowy peak summit against clear blue sky

Transition Flexibility

Acquirers considering operational changes post-transaction often evaluate whether subcontractor documentation supports flexibility or creates constraints. Contract terms that support smooth transitions (appropriate termination provisions, reasonable notice periods, clear intellectual property ownership) may boost perceived flexibility.

Conversely, subcontractor documentation that creates transition friction may concern buyers. Long-term exclusive arrangements, unclear intellectual property provisions, restrictive termination clauses, or inadequate confidentiality protections can all complicate post-acquisition integration and may reduce buyer willingness to pay premium valuations.

Industry and Geographic Variations in Documentation Requirements

Subcontractor documentation requirements and buyer expectations vary significantly across industries and geographies. Applying one-size-fits-all documentation practices without considering these variations can create both compliance gaps and unnecessary complexity.

Industry-Specific Considerations

Technology and Software Services: Technology companies often rely heavily on specialized subcontractors for development, design, and implementation work. Buyers in this sector typically focus intensely on intellectual property assignment documentation, ensuring clear ownership of code and deliverables. Non-disclosure and confidentiality provisions receive heightened scrutiny given the competitive sensitivity of technical work.

Professional Services: Consulting, accounting, and legal services firms using subcontractors face particular scrutiny around credentials verification and professional liability. Documentation should typically address professional licensing, errors and omissions insurance, and client confidentiality obligations that flow through to subcontractors.

Construction and Trades: This sector faces extensive regulatory requirements around subcontractor documentation, including prevailing wage compliance, safety certifications, bonding requirements, and license verification. Buyers in construction transactions often employ specialized due diligence focused on subcontractor compliance documentation.

Healthcare and Related Services: HIPAA compliance documentation, background check records, and credentialing verification add complexity to subcontractor documentation in healthcare-adjacent businesses. Buyers typically apply rigorous standards given the regulatory consequences of compliance failures.

Geographic Regulatory Variations

State-level differences in classification tests create documentation complexity for companies operating across multiple jurisdictions:

California: The ABC test under AB5 creates the strictest classification standards in the country, presuming worker status as employee unless all three prongs are satisfied. Companies with California-based subcontractors need documentation specifically addressing ABC test factors.

Massachusetts, New Jersey, Illinois: These states apply tests similar to California’s ABC standard, requiring careful documentation attention.

Texas, Florida, most other states: Generally follow federal IRS standards with some state-specific variations. Documentation aligned with IRS guidance typically satisfies these states’ requirements.

For companies with subcontractors across multiple states, we typically recommend maintaining documentation that satisfies the most stringent applicable standard (usually California’s ABC test) rather than attempting jurisdiction-specific documentation approaches.

Documentation Frameworks That May Demonstrate Compliance Discipline

Moving from understanding buyer expectations to practical implementation, specific documentation frameworks may demonstrate the compliance discipline that sophisticated buyers often seek. These frameworks typically address both legal requirements and operational measures.

Contract Documentation Standards

Effective subcontractor contracts generally address classification compliance while supporting operational objectives. We recommend contract documentation that includes:

Scope Definition Elements:

  • Specific deliverable descriptions rather than role descriptions
  • Project timelines with defined completion criteria
  • Quality standards expressed as outcome requirements
  • Change order procedures for scope modifications

Independence Provisions:

  • Explicit statements of independent contractor status
  • Acknowledgment of subcontractor responsibility for taxes, insurance, and benefits
  • Freedom to provide services to other clients
  • Control over methods used to achieve deliverables

Operational Requirements:

  • Deliverable acceptance criteria
  • Communication and reporting expectations
  • Confidentiality and data protection requirements
  • Intellectual property ownership provisions

Relationship Management:

  • Payment terms tied to deliverable completion
  • Performance issue escalation procedures
  • Contract modification processes
  • Termination provisions respecting project-based relationships

Onboarding Documentation

Beyond contracts, systematic onboarding documentation may demonstrate operational discipline that carries throughout the subcontractor relationship. Effective onboarding frameworks typically include:

Qualification Verification:

  • Capability assessment documentation
  • Insurance verification records
  • Reference or work sample evaluation
  • Compliance certification collection

Engagement Setup:

  • Project scope confirmation
  • Deliverable schedule agreement
  • Communication protocol establishment
  • Access and resource provision documentation

Compliance Documentation:

  • W-9 or appropriate tax documentation
  • Independent contractor questionnaire completion
  • Classification analysis documentation
  • Business entity verification

Performance Management Documentation

Ongoing performance documentation may demonstrate operational oversight without crossing classification boundaries. Effective frameworks typically focus on:

Deliverable Tracking:

  • Milestone completion documentation
  • Quality acceptance records
  • Change order documentation
  • Payment authorization records

Issue Resolution:

  • Performance concern documentation
  • Corrective action records
  • Escalation documentation
  • Relationship conclusion records when necessary

Common Documentation Implementation Failures

Understanding common failure modes helps business owners avoid pitfalls that can undermine documentation efforts. Implementation failures are common and can create significant operational disruption.

Template-Only Approaches: Some companies implement comprehensive contract templates but fail to ensure contracts reflect actual working relationships. Sophisticated buyers often interview subcontractors during due diligence. Contracts that describe project-based deliverables while subcontractors describe ongoing employment-like arrangements create serious problems and may actually worsen legal exposure.

Inconsistent Application: Documentation standards applied to some subcontractors but not others signal operational inconsistency. Buyers may question why certain relationships lack documentation and assume the worst about undocumented arrangements. Based on our observations, approximately 40% of businesses attempting comprehensive documentation overhauls encounter significant challenges with incomplete implementation due to resource constraints or relationship complexity.

Outdated Documentation: Original contracts that haven’t been updated as relationships changed create gaps between documentation and reality. Multi-year relationships operating under initial project scopes that no longer reflect actual work performed raise classification concerns.

Missing Renewal Documentation: Ongoing relationships require periodic reaffirmation of independent contractor status. Many companies fail to document annual renewals or scope updates, creating documentation gaps that concern buyers.

Inadequate Classification Analysis: Simply labeling workers as subcontractors and having contracts in place doesn’t constitute classification analysis. Documenting the actual analysis (why specific workers qualify as independent contractors under applicable tests) provides stronger protection.

Documentation Decay: Without ongoing maintenance processes, documentation quality typically degrades over time. Scope creep, informal relationship changes, and staff turnover all contribute to widening gaps between documented arrangements and operational reality. We estimate that without dedicated maintenance resources, documentation becomes materially outdated within 12-18 months for most businesses.

Evaluating Workforce Structure Alternatives

Before investing heavily in subcontractor documentation, business owners should evaluate whether subcontractor relationships represent the optimal workforce structure for their situation. In some cases, alternative approaches may better serve your operational needs and risk tolerance, particularly for relationships that don’t clearly meet independent contractor tests.

Full-Time Employment: Higher fixed costs but cleaner compliance profile. May be appropriate for core functions where long-term, controlled relationships are necessary. Converting problematic subcontractor relationships to employee status eliminates misclassification risk entirely, though it increases payroll taxes by 7.65% (employer FICA portion) plus benefits costs.

Staffing Agencies: Transfer classification risk to the agency but add cost layers typically ranging from 20-30% markup over direct labor costs. Can simplify documentation requirements while maintaining workforce flexibility. This approach works best when short-term flexibility is crucial and classification risk is high.

Professional Employer Organizations (PEOs): Provide employment infrastructure for small companies lacking HR capabilities. May be relevant for converting problematic subcontractor relationships while maintaining some flexibility.

Fractional Professionals: Part-time professional arrangements increasingly common for CFO, CMO, and other executive functions. Generally cleaner classification than traditional subcontracting for ongoing advisory relationships.

The optimal mix depends on your specific industry, operational needs, and exit timeline. Companies planning exits within two to three years may benefit from simplifying workforce structures even at higher cost, while those with longer horizons have time to build robust documentation for more complex arrangements.

When evaluating alternatives, consider:

  • Employee conversion works better when relationships don’t clearly meet contractor tests, when direct control is operationally necessary, or when long-term relationships exist
  • Staffing agencies work better when short-term flexibility is paramount and cost markup is acceptable relative to risk transfer
  • Subcontractor arrangements with robust documentation work best for genuine project-based work with clearly independent relationships

Building Documentation Systems That May Reduce Transaction Friction

Implementing subcontractor documentation frameworks requires systematic approaches that create sustainable practices rather than one-time compliance exercises. Business owners preparing for exits should focus on building documentation systems that demonstrate ongoing operational discipline.

Centralized Documentation Management

Scattered subcontractor documentation creates due diligence challenges and may signal organizational weakness. Implementing centralized documentation management (whether through dedicated contract management systems, organized digital filing structures, or systematic physical filing approaches) typically demonstrates operational maturity.

Centralized systems should capture complete documentation histories for each subcontractor relationship, including original contracts, amendments, scope changes, performance records, payment histories, and relationship conclusion documentation. This comprehensive documentation supports due diligence efficiency while demonstrating systematic operational practices.

Regular Documentation Audits

Periodic documentation audits may identify gaps before they become due diligence problems. We recommend annual reviews of subcontractor documentation that verify contract currency, confirm classification compliance, identify documentation gaps, and ensure consistent application of documentation standards across all subcontractor relationships.

These audits should evaluate whether existing documentation reflects current relationship realities, whether contracts require updates based on scope or term changes, whether all required compliance documentation remains current, and whether documentation practices have been consistently applied across the subcontractor program.

Classification Compliance Reviews

Beyond documentation audits, periodic classification compliance reviews may assess whether subcontractor relationships continue to meet independent contractor criteria. These reviews should examine:

  • Whether relationship realities match contract documentation
  • Whether control levels have shifted toward employment-like arrangements
  • Whether payment patterns suggest employment relationships
  • Whether any subcontractors should transition to employee status

Documenting these reviews (even when they confirm appropriate classification) may demonstrate ongoing compliance attention that sophisticated buyers value.

Realistic Implementation Costs and Timelines

Understanding true implementation costs helps business owners make informed decisions about documentation investments. Many businesses underestimate the full resource requirements.

Full Cost Accounting

Direct Costs:

  • Legal counsel engagement for template development and compliance review: $3,000-$15,000 depending on complexity, number of relationships, and state variations requiring review
  • Document management systems: $500-$2,000 annually
  • Ongoing compliance monitoring and legal updates: $1,000-$5,000 annually

Indirect Costs Often Overlooked:

  • Executive/owner time for oversight and decision-making: 20-40 hours × $200/hour effective rate = $4,000-$8,000
  • Internal staff time for documentation compilation and maintenance: 10-20 hours × $50/hour = $500-$1,000 initial, plus ongoing
  • Opportunity cost of time diverted from revenue activities: varies significantly
  • Potential relationship disruption during documentation overhaul: some subcontractors may resist detailed documentation requirements

Realistic First-Year Total: $9,500-$30,000 for businesses with 10-25 subcontractor relationships, including all direct and indirect costs.

Ongoing Annual Maintenance: $2,500-$10,000 depending on subcontractor volume and relationship complexity.

Realistic Timeline Expectations

These timelines assume reasonably organized existing documentation and available internal resources. Companies with extensive or poorly documented subcontractor relationships should expect longer implementation periods:

Initial Inventory and Gap Analysis (30-60 days):

  • Best case: 30 days with fewer than 10 relationships and organized existing files
  • Typical case: 45-60 days with 10-25 relationships and scattered documentation
  • Challenging case: 90+ days with extensive relationships or multiple locations

Template Development and Legal Review (60-90 days):

  • Concurrent with inventory work where possible
  • May require multiple revision cycles with legal counsel
  • Multi-state operations add complexity

Implementation and Rollout (90-180 days):

  • Phased approach typically more successful than big-bang implementation
  • Subcontractor communication and re-contracting takes time
  • Resistance from established subcontractors is common

Total Implementation: 6-12 months for most businesses in our target revenue range, not the 90 days sometimes suggested.

Actionable Takeaways

Business owners planning exits should consider implementing specific subcontractor documentation improvements based on their timeline and current documentation state:

Immediate Actions (Target: 30-60 Days):

  • Inventory all current subcontractor relationships and associated documentation
  • Identify documentation gaps in existing contracts
  • Verify current compliance documentation (W-9s, insurance certificates) is complete and current
  • Establish centralized documentation repository if not already in place
  • Assess whether each relationship genuinely qualifies as independent contractor—if not, consider employment conversion before proceeding
  • Estimated resource requirement: 15-30 hours of internal time depending on subcontractor count

Short-Term Improvements (Target: 90-180 Days):

  • Engage employment counsel for template development and compliance review
  • Update or replace non-compliant contract templates with comprehensive documentation
  • Implement standardized onboarding checklists and documentation requirements
  • Create systematic performance documentation processes
  • Conduct classification compliance review for all existing relationships
  • Convert problematic relationships to employee status rather than attempting to document them as contractors
  • Estimated resource requirement: $3,000-$15,000 legal counsel plus 30-50 hours of internal time

Ongoing Practices (Implement Permanently):

  • Apply consistent documentation standards to all new subcontractor engagements
  • Conduct annual documentation audits and classification reviews
  • Maintain complete documentation histories throughout relationship lifecycles
  • Update documentation practices as compliance requirements change
  • Estimated resource requirement: 8-15 hours annually per 10 subcontractor relationships plus $1,000-$5,000 annual legal/compliance costs

Exit Preparation Activities (12-24 Months Before Sale):

  • Compile comprehensive subcontractor documentation packages for due diligence
  • Address any identified compliance concerns proactively
  • Document subcontractor program metrics demonstrating operational flexibility
  • Prepare summary materials explaining subcontractor program sophistication
  • Consider engaging employment counsel for pre-due diligence review
  • Simplify workforce structure where complexity creates unnecessary risk

Conclusion

Subcontractor documentation represents an area where systematic attention may demonstrate operational sophistication to potential buyers. The same documentation practices that help reduce misclassification risk also tend to signal the organizational discipline that experienced acquirers often associate with well-managed companies.

For business owners in the $2M-$20M revenue range, subcontractor documentation often reveals the gap between operational informality that worked during growth phases and the systematic practices that M&A transactions typically require. Addressing this gap proactively (implementing comprehensive documentation frameworks, maintaining consistent practices, and conducting regular compliance reviews) may position your company more favorably for buyer evaluation, though the actual impact varies significantly based on buyer priorities and your specific circumstances.

But documentation alone isn’t sufficient. The underlying relationships must genuinely qualify as independent contractor arrangements, documentation must accurately reflect working realities, and practices must be consistently maintained over time. Systematic documentation demonstrates operational discipline, but only when that discipline actually exists.

Documentation implementation carries real risks. Creating evidence that worsens misclassification exposure if relationships don’t genuinely qualify, incomplete implementation that signals operational inconsistency, and documentation decay if not maintained: these failure modes are common and can be costly. Before investing in documentation improvements, honestly assess whether your subcontractor relationships meet legal requirements. If they don’t, converting to employee status may be wiser than attempting to document problematic arrangements.

Your subcontractor documentation tells a story about how you run your business. Make sure it’s a story that accurately represents the operational discipline you’ve built and one that doesn’t create more problems than it solves.