Capabilities

Your capability statements are the heart of Cothon's AI matching and proposal generation. These statements describe what your company does, how you do it, and why you're qualified. The AI uses this content to match RFP requirements, score your fit for opportunities, and generate proposal narratives.

Why Capabilities Matter

AI Matching Foundation

When analyzing an RFP, Cothon's AI compares each requirement against your capability statements:

Semantic Analysis: The AI understands meaning, not just keywords. It recognizes that "cloud infrastructure modernization" matches requirements for "legacy system migration to public cloud platforms" even though exact phrases differ.

Confidence Scoring: Each capability match receives a confidence score (0-100%):

• 90-100%: Strong match, suitable for auto-generated proposal content
• 70-89%: Good match, suitable with human review
• 50-69%: Partial match, may need qualification or teaming
• <50%: Weak match, indicates gap

Match Quality: Detailed, specific capability statements produce higher confidence scores than vague, generic ones.

Example:

❌ Generic Capability: "We provide IT consulting services."

• RFP Requirement: "Contractor must have expertise in AWS cloud migration including EC2, S3, RDS, and CloudFormation infrastructure-as-code."
• AI Match: 35% confidence (too vague, no specific AWS experience mentioned)

✅ Specific Capability: "We provide cloud migration services specializing in AWS infrastructure modernization. Our certified team (15 AWS Solutions Architects) has migrated 120+ applications to AWS using infrastructure-as-code (Terraform, CloudFormation), including EC2 compute, S3 storage, RDS databases, and Lambda serverless. We follow AWS Well-Architected Framework with average 40% cost reduction post-migration."

• Same RFP Requirement
• AI Match: 95% confidence (specific AWS services mentioned, IaC tools match, quantified experience)

Proposal Content Generation

The AI pulls directly from your capability statements to generate proposal sections:

Executive Summary: High-level capability overview becomes opening summary

Technical Approach: Detailed capability descriptions become methodology and approach sections

Corporate Experience: Capability areas + past performance become corporate experience narratives

Team Qualifications: Capability statements reference personnel, tools, and certifications

Why We're Different: Unique aspects of capabilities become differentiators section

Example Flow:

Your Capability Statement:

"We specialize in cybersecurity assessment services using NIST Cybersecurity Framework (CSF) and NIST 800-53 controls. Our team of 12 CISSP-certified security analysts conducts vulnerability assessments, penetration testing, and security architecture reviews for federal agencies. We've completed 85 security assessments totaling $12M in contract value with zero security incidents or data breaches. Our methodology includes automated vulnerability scanning (Nessus, Qualys), manual penetration testing, and detailed remediation roadmaps with prioritized recommendations."

AI-Generated Proposal Section (Technical Approach):

"Our approach to cybersecurity assessment is grounded in NIST Cybersecurity Framework (CSF) and NIST 800-53 control standards, ensuring alignment with federal security requirements. Our 12 CISSP-certified security analysts will conduct comprehensive vulnerability assessments and penetration testing using industry-leading tools including Nessus and Qualys for automated scanning, complemented by manual penetration testing to identify complex vulnerabilities automated tools may miss.

We follow a proven methodology refined over 85 federal security assessments totaling $12M in contract value. Our track record includes zero security incidents or data breaches across all engagements, demonstrating our commitment to secure assessment practices. Each assessment concludes with detailed remediation roadmaps featuring prioritized recommendations aligned with risk severity and business impact..."

Result: Rich, specific proposal content that directly addresses requirements.

Discovery and Filtering

Well-written capability statements improve opportunity discovery:

Keyword Matching: Procurement officers search supplier databases by keywords. Specific terminology increases your visibility.

UNSPSC Enrichment: Capability statements reinforce your UNSPSC code selections, improving semantic relevance.

Gap Identification: The AI compares your capabilities against opportunity requirements to identify gaps, suggesting teaming partners or capability development areas.

Capability Structure Framework

The 5W1H Formula

Effective capability statements answer six key questions:

What: What service or product do you provide? Who: Who delivers it (team, expertise, certifications)? How: How do you deliver (methodology, tools, process)? Where: Where do you deliver (geographic coverage, facilities)? When: When have you delivered (experience, volume, timeline)? Why: Why are you different (outcomes, quality, innovation)?

Example Application:

Capability: Bridge Inspection and Rehabilitation

• What: "We provide bridge inspection, structural assessment, and rehabilitation design services for highway and municipal bridges."

• Who: "Our team includes 8 Professional Engineers (P.Eng.) specializing in structural engineering, 4 OSPE Bridge Inspector-certified technologists, and 12 field inspection technicians."

• How: "We use non-destructive evaluation techniques including ground-penetrating radar, ultrasonic testing, and infrared thermography, combined with visual inspections per CSA S6 standards. Our rehabilitation designs emphasize life-cycle cost optimization and minimal traffic disruption."

• Where: "We operate across Ontario, Quebec, and Atlantic Canada from offices in Toronto, Montreal, and Halifax with mobile inspection units enabling rapid deployment."

• When: "Since 2015, we've inspected 850+ bridges and designed 120 rehabilitation projects totaling $95M in construction value, maintaining 98% on-time report delivery."

• Why: "Our unique strength is predictive bridge health modeling using AI analysis of inspection data, enabling proactive maintenance planning that extends bridge life 15-20% compared to reactive approaches."

Complete Capability Statement:

"We provide bridge inspection, structural assessment, and rehabilitation design services for highway and municipal bridges. Our team includes 8 Professional Engineers (P.Eng.) specializing in structural engineering, 4 OSPE Bridge Inspector-certified technologists, and 12 field inspection technicians.

We use non-destructive evaluation techniques including ground-penetrating radar, ultrasonic testing, and infrared thermography, combined with visual inspections per CSA S6 standards. Our rehabilitation designs emphasize life-cycle cost optimization and minimal traffic disruption through innovative solutions like carbon fiber reinforcement and rapid-curing concrete.

Operating across Ontario, Quebec, and Atlantic Canada from offices in Toronto, Montreal, and Halifax, our mobile inspection units enable rapid deployment to remote bridge sites. Since 2015, we've inspected 850+ bridges and designed 120 rehabilitation projects totaling $95M in construction value, maintaining 98% on-time report delivery and zero safety incidents.

Our unique strength is predictive bridge health modeling using AI analysis of inspection data (machine learning pattern recognition of degradation), enabling proactive maintenance planning that extends bridge life 15-20% compared to reactive approaches. This innovation saved our municipal clients an estimated $8M in deferred rehabilitation costs."

Capability Components

Break down each major capability into components:

Core Competency: What is the fundamental service/product?

Technical Capabilities: Specific technical skills, methodologies, technologies

Process Capabilities: How you execute (project management, quality assurance, delivery model)

Domain Expertise: Industry or sector specialization

Scale Capabilities: Size and complexity you can handle

Geographic Capabilities: Where you can deliver

Support Capabilities: Post-delivery support, maintenance, training

Example - IT Application Development Capability:

Core Competency:

"Custom software application development for federal government clients"

Technical Capabilities:

"Full-stack development using React/Node.js, Python/Django, Java/Spring Boot. Cloud-native architecture on AWS and Azure. RESTful API design, microservices patterns, and event-driven integration. Expertise in government platforms including GC Notify, Cloud.canada.ca, and GCForms."

Process Capabilities:

"Agile Scrum delivery with 2-week sprints, daily standups, and continuous integration/continuous deployment (CI/CD) pipelines using GitLab CI and Jenkins. Test-driven development (TDD) with 80%+ code coverage. Security-first design following OWASP Top 10 and ITSG-33 controls."

Domain Expertise:

"Specialized in case management systems, citizen engagement portals, and grant/contribution management applications for federal departments including ISED, ESDC, and IRCC."

Scale Capabilities:

"Deliver projects ranging from $200K (3-month development cycles, 4-person teams) to $5M (18-month programs, 20-person teams). Concurrent project capacity: 6 active projects."

Geographic Capabilities:

"Development teams based in Ottawa and Montreal. Provide on-site presence at client facilities in NCR (National Capital Region) and regional offices as required."

Support Capabilities:

"Post-launch support and maintenance including 24/7 on-call for production issues (15-minute response time), monthly security patching, quarterly feature enhancements, and annual technology updates."

Writing Effective Capability Statements

Be Specific, Not Generic

Generic vs. Specific Examples:

❌ Generic: "We provide project management services."

✅ Specific: "We provide project management office (PMO) services for federal IT infrastructure projects using PMI Project Management Body of Knowledge (PMBOK) and Agile methodologies. Our 18 PMP-certified project managers have delivered 65 IT projects totaling $180M with average on-time completion rate of 94% and average budget variance of <3%."

❌ Generic: "We offer cybersecurity solutions."

✅ Specific: "We provide cybersecurity risk assessment and Authority to Operate (ATO) package development services for federal cloud systems. Our team of 8 CISSP-certified consultants specializes in NIST 800-53 security controls implementation, FedRAMP compliance, and cloud security architecture on AWS and Azure. We've supported 22 ATO submissions with 95% first-time approval rate, average timeline of 6 months per ATO."

❌ Generic: "Our company does environmental consulting."

✅ Specific: "We conduct Environmental Impact Assessments (EIA) under Canadian Environmental Assessment Act (CEAA 2012) for transportation and energy infrastructure projects. Our multidisciplinary team includes 6 Environmental Professionals (EP), 3 wildlife biologists, 2 archaeologists, and 4 Indigenous engagement specialists. Since 2018, we've completed 35 EIAs for projects totaling $2.5B in capital value, including 12 CEAA panel reviews with zero ministerial rejections."

Use Numbers and Metrics

Quantify everything possible:

Team Size: "12 software developers" vs. "development team"

Experience Volume: "Completed 85 projects totaling $45M" vs. "extensive experience"

Timeline: "Average 8-month delivery cycle" vs. "timely delivery"

Quality: "98% on-time delivery rate" vs. "reliable delivery"

Outcomes: "Average 35% cost reduction for clients" vs. "cost-effective solutions"

Scale: "Projects ranging $100K-$8M" vs. "projects of all sizes"

Example with Metrics:

"We provide data center migration services specializing in physical-to-cloud and cloud-to-cloud migrations. Our team of 25 certified cloud engineers (15 AWS, 10 Azure) has migrated 3,200+ servers and 850TB of data across 48 data center consolidation projects totaling $72M in contract value. Average project timeline: 12 months for 500-server migrations. Average downtime during cutover: 4 hours (99.95% uptime maintained). Average cost savings for clients: 38% reduction in infrastructure costs post-migration. Zero data loss incidents across all migrations."

Include Tools and Technologies

Specific tools, platforms, and methodologies demonstrate depth:

Software Development:

• Languages: "Python, Java, JavaScript, TypeScript, Go"
• Frameworks: "React, Angular, Node.js, Django, Spring Boot"
• Databases: "PostgreSQL, MongoDB, DynamoDB, Redis"
• Cloud: "AWS (EC2, S3, Lambda, RDS), Azure (VMs, Blob Storage, Functions), GCP"
• DevOps: "Docker, Kubernetes, GitLab CI, Jenkins, Terraform, Ansible"

Engineering:

• Design Software: "AutoCAD Civil 3D, MicroStation, ArcGIS, HEC-RAS"
• Analysis Tools: "SAP2000, ETABS, RISA-3D, STAAD.Pro"
• Standards: "CSA S6-19, AASHTO LRFD, NBC 2020, OBC"
• Methods: "Finite Element Analysis, computational fluid dynamics"

Project Management:

• Methodologies: "PMI PMBOK 7, Agile Scrum, SAFe 5.1, PRINCE2"
• Tools: "Microsoft Project, Jira, Asana, Monday.com, Smartsheet"
• Frameworks: "Earned Value Management (EVM), Critical Path Method (CPM)"

Why It Matters: When an RFP specifies "Contractor must have experience with Terraform infrastructure-as-code," the AI looks for "Terraform" in your capabilities. Mentioning specific tools dramatically increases match confidence.

Reference Standards and Frameworks

Government procurement values compliance with standards:

Quality Standards:

• ISO 9001:2015 (Quality Management)
• ISO 14001:2015 (Environmental Management)
• ISO 45001:2018 (Health & Safety)
• ISO/IEC 27001:2013 (Information Security)

Government Standards:

• NIST Cybersecurity Framework (CSF)
• NIST 800-53 (Security and Privacy Controls)
• FedRAMP (Cloud Security)
• ITSG-33 (IT Security Risk Management)
• PBMM (Protected B, Medium Integrity, Medium Availability)

Industry Standards:

• PMI PMBOK (Project Management)
• ITIL v4 (IT Service Management)
• TOGAF (Enterprise Architecture)
• COBIT (IT Governance)

Engineering Standards:

• CSA (Canadian Standards Association) - various standards
• AASHTO (American Association of State Highway and Transportation Officials)
• ASTM (American Society for Testing and Materials)
• NBC (National Building Code of Canada)

Example:

"We design water treatment facilities following CSA B128 series standards (Design and Construction of Health Care Facilities), NSF/ANSI standards for drinking water treatment, and provincial regulatory requirements (O.Reg 170/03 in Ontario, Q.2 r.19 in Quebec). Our designs incorporate SCADA systems compliant with NIST 800-82 (Industrial Control Systems Security). All projects adhere to ISO 9001:2015 quality management processes with formal design reviews, third-party peer review, and comprehensive commissioning."

Describe Methodology and Process

How you deliver is as important as what you deliver:

Project Phases: "Discovery → Design → Development → Testing → Deployment → Support"

Quality Assurance: "Peer review at every design milestone, independent QA testing, client UAT"

Risk Management: "Formal risk register, weekly risk review, escalation protocols"

Communication: "Weekly status reports, bi-weekly steering committee meetings, 24/7 on-call support"

Example - Consulting Methodology:

"Our management consulting approach follows a five-phase methodology:

Phase 1 - Discovery (Weeks 1-2): Stakeholder interviews (15-20 key personnel), document review, current state assessment, and identification of pain points. Deliverable: Current State Report with gap analysis.

Phase 2 - Analysis (Weeks 3-4): Root cause analysis using fishbone diagrams and 5 Whys, benchmarking against industry best practices, and identification of improvement opportunities. Deliverable: Detailed Findings Report with quantified impact.

Phase 3 - Design (Weeks 5-6): Future state design through facilitated workshops, process mapping (BPMN 2.0 notation), technology requirements definition, and change management planning. Deliverable: Future State Blueprint and Implementation Roadmap.

Phase 4 - Implementation Support (Weeks 7-12): Change management execution, training development and delivery, process rollout, and performance monitoring. Deliverable: Implementation Progress Reports and Training Materials.

Phase 5 - Transition (Weeks 13-14): Knowledge transfer, documentation finalization, lessons learned workshop, and sustainability planning. Deliverable: Final Report, Knowledge Base, and Sustainability Plan.

Throughout all phases, we maintain weekly steering committee updates and a shared project portal for transparent progress tracking."

Include Outcomes and Results

Demonstrate the value you deliver:

Cost Outcomes: "Average 30% cost reduction for clients"

Time Outcomes: "95% on-time delivery rate, average 15% faster than industry baseline"

Quality Outcomes: "99.7% defect-free delivery, zero critical incidents"

Performance Outcomes: "Applications support 10,000+ concurrent users with <200ms response time"

Business Outcomes: "Enabled $5M annual revenue increase for client through system efficiency"

Example:

"We provide business process re-engineering services for government program delivery. Our methodology combines Lean Six Sigma principles with human-centered design, resulting in average outcomes of:

• 40% reduction in process cycle time
• 35% decrease in operating costs
• 50% improvement in client satisfaction scores
• 25% reduction in error rates

Recent example: For a provincial benefits program serving 80,000 citizens, we redesigned the application process, reducing average processing time from 45 days to 18 days (60% improvement) while maintaining 99.2% accuracy. This improvement enabled the program to handle 30% increased demand with existing staffing levels, saving an estimated $2.3M annually."

Organizing Your Capabilities

Core Capabilities (Primary)

Your top 5-8 service offerings representing 80%+ of revenue and deep expertise:

Characteristics:

• Substantial past performance (10+ contracts)
• Deep expertise (5+ years experience)
• Can deliver independently (no partners required)
• Strong team credentials and certifications
• Proven track record and references

Example - IT Consulting Firm Core Capabilities:

1. Cloud Infrastructure Migration (AWS, Azure)
2. Cybersecurity Risk Assessment and ATO Development
3. Custom Application Development (Full-Stack Web)
4. IT Project Management and PMO Services
5. DevSecOps Implementation and CI/CD Pipeline Development

Secondary Capabilities

Adjacent or emerging services where you have capability but less depth:

Characteristics:

• Moderate past performance (3-10 contracts)
• Growing expertise (2-5 years experience)
• May require teaming for large/complex projects
• Building team credentials
• References available but limited

Example - Same IT Firm Secondary Capabilities:

1. Data Analytics and Business Intelligence
2. IT Service Management (ITIL-based)
3. Enterprise Architecture (TOGAF)
4. Change Management and Training
5. GIS (Geographic Information Systems) Solutions

Emerging Capabilities

New service areas you're developing:

Characteristics:

• Limited past performance (1-3 projects or pilots)
• Early expertise (6 months - 2 years)
• Requires partnerships for delivery
• Acquiring certifications and credentials
• Building case studies

Example - Same IT Firm Emerging Capabilities:

1. Artificial Intelligence / Machine Learning Solutions
2. Blockchain for Government Applications
3. Internet of Things (IoT) Platform Development

Capability Categories

Organize capabilities by category for clarity:

By Service Type:

• Consulting
• Design
• Implementation
• Support & Maintenance
• Training

By Technical Domain:

• Infrastructure
• Applications
• Security
• Data
• Integration

By Industry Vertical:

• Healthcare
• Transportation
• Justice
• Education
• Environment

By Project Phase:

• Assessment & Planning
• Design & Architecture
• Development & Implementation
• Testing & Quality Assurance
• Deployment & Transition
• Operations & Maintenance

Capability Statement Templates

Template 1: Service Capability

Structure:

"We provide [SERVICE] for [CLIENT TYPE] using [METHODOLOGY/TECHNOLOGY]. Our team of [NUMBER] [ROLE/CERTIFICATION] has [QUANTIFIED EXPERIENCE]. We deliver [OUTCOMES/RESULTS] through [UNIQUE APPROACH/DIFFERENTIATOR]."

Example:

"We provide environmental site assessment (ESA) services for federal real property transactions using CSA Z768-01 Phase I ESA standard and CSA Z769-00 Phase II ESA standard. Our team of 12 Environmental Professionals (EP) has completed 340 ESAs across 15 federal departments totaling $8.5M in contract value. We deliver comprehensive risk assessments with average 3-week turnaround (40% faster than industry average) through our proprietary contamination database of 50,000+ federal sites, enabling rapid historical research and risk profiling."

Template 2: Technical Capability

Structure:

"We [ACTION VERB] [TECHNICAL CAPABILITY] for [USE CASE] using [SPECIFIC TOOLS/PLATFORMS]. Our expertise includes [TECHNICAL DETAILS]. We have [QUANTIFIED EXPERIENCE] with [PERFORMANCE METRICS]."

Example:

"We develop cloud-native microservices architectures for federal application modernization using container orchestration (Kubernetes, Docker Swarm) on AWS EKS and Azure AKS. Our expertise includes API gateway design (Kong, Apigee), service mesh implementation (Istio, Linkerd), and distributed tracing (Jaeger, Zipkin). We have containerized 85 legacy applications comprising 400+ microservices, achieving average 60% infrastructure cost reduction and 10x deployment frequency improvement."

Template 3: Domain Expertise Capability

Structure:

"We specialize in [DOMAIN/SECTOR] with [YEARS] experience serving [CLIENT TYPES]. Our expertise includes [SPECIFIC DOMAIN KNOWLEDGE]. We have [QUANTIFIED DOMAIN EXPERIENCE] delivering [TYPICAL PROJECTS]."

Example:

"We specialize in healthcare IT systems with 18 years serving provincial health ministries, regional health authorities, and hospital networks. Our expertise includes Electronic Medical Record (EMR) integration, Health Level 7 (HL7) FHIR standards implementation, PHIPA/PIPEDA privacy compliance, and clinical workflow optimization. We have integrated 45 healthcare IT systems across 12 provinces serving 8M patient records, delivering projects ranging from $500K diagnostic imaging integration to $12M province-wide EMR implementations."

Template 4: Process/Methodology Capability

Structure:

"We apply [METHODOLOGY/FRAMEWORK] to [SERVICE AREA] ensuring [QUALITY/COMPLIANCE OUTCOME]. Our process includes [KEY PHASES]. We have [QUANTIFIED EXPERIENCE] with [PROCESS METRICS]."

Example:

"We apply ISO 9001:2015 quality management principles to engineering design services ensuring compliance, traceability, and client satisfaction. Our process includes formal design reviews at 30%, 60%, and 90% completion milestones, independent peer review by Professional Engineers not involved in the design, and comprehensive quality checklists aligned with applicable codes and standards. We have delivered 220 engineering designs under ISO 9001 QMS with zero design defects leading to construction rework, 98% first-submission approval rate by authorities having jurisdiction, and 4.8/5.0 average client satisfaction score."

Linking Capabilities to Other Profile Elements

Capabilities + Past Performance

Every core capability should be supported by past performance:

Strong Linkage Example:

Capability Statement:

"We provide IT security risk assessments following NIST 800-53 control framework..."

Supporting Past Performance:

• Project 1: "Security Risk Assessment - Department of Justice" ($450K, 2023)
• Project 2: "NIST 800-53 Control Implementation - Public Safety Canada" ($680K, 2022)
• Project 3: "Cloud Security Assessment - Transport Canada" ($320K, 2024)

AI Impact: When matching RFP requirements for "NIST 800-53 security assessment," the AI sees both the capability statement AND three past performance examples, resulting in 95%+ confidence score.

Weak Linkage Example:

Capability Statement:

"We provide blockchain application development..."

Supporting Past Performance:

• (No blockchain projects listed)

AI Impact: The capability claim lacks evidence. Confidence score drops to 40-50% even if the capability statement is well-written.

Capabilities + Certifications

Link certifications to capabilities to demonstrate accreditation:

Example:

Capability Statement:

"We provide ISO 27001 consulting services helping federal agencies achieve information security management system (ISMS) certification. Our team of 6 ISO 27001 Lead Auditors and 4 Certified Information Systems Security Professionals (CISSP) has supported 18 federal departments through ISO 27001 certification processes, with 100% first-attempt certification success rate."

Supporting Certifications:

• Company: ISO 27001:2013 certified (our own ISMS)
• Personnel: 6 ISO 27001 Lead Auditor certifications, 4 CISSP certifications

AI Impact: Capability + certification creates reinforcing evidence, increasing match confidence.

Capabilities + UNSPSC Codes

Align capabilities with your selected UNSPSC codes:

Example:

UNSPSC Code: 81.10.15.02 - Bridge Design Services

Matching Capability Statement:

"We provide bridge design services for highway and municipal infrastructure including new bridge design, rehabilitation and retrofit design, and seismic upgrades. Our structural engineering team has designed 65 bridges ranging from 15m single-span pedestrian bridges to 450m multi-span highway structures..."

AI Impact: When opportunities tagged with UNSPSC 81.10.15.02 appear, the AI matches both the code AND the detailed capability statement, producing high relevance scores.

Misalignment Example:

UNSPSC Code: 81.10.15.02 - Bridge Design Services

Capability Statement:

"We provide general civil engineering consulting services for infrastructure projects."

AI Impact: The capability is too vague to support the specific UNSPSC code. Match confidence drops despite code alignment.

AI-Optimized Writing Tips

Use Government Terminology

Mirror the language used in government RFPs:

Government Term → Use This:

• "Cloud migration" (not "moving to the cloud")
• "Application modernization" (not "app updates")
• "Authority to Operate (ATO)" (not "security approval")
• "Professional Engineer (P.Eng.)" (not "licensed engineer")
• "Statement of Work (SOW)" (not "project scope")
• "Deliverable" (not "output" or "product")

Why: The AI and procurement officers search using these terms. Matching terminology improves discoverability and relevance.

Include Acronyms and Variations

Provide full terms plus acronyms on first use:

Example:

"We provide Electronic Health Record (EHR) integration services, also known as Electronic Medical Record (EMR) systems, connecting clinical applications using Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR) standards."

Why: Different RFPs use different terms. "EHR" vs "EMR", "cloud computing" vs "cloud services". Including variations improves matching.

Structure for Scannability

Use formatting to make capabilities scannable:

Bullet Points for Lists:

"Our cybersecurity services include:

• Vulnerability assessments and penetration testing
• Security architecture design and review
• Incident response and forensics
• Security awareness training"

Bold for Emphasis:

"We have completed 85 security assessments for 22 federal departments with zero security breaches during or after our engagements."

Short Paragraphs:

• Aim for 3-5 sentences per paragraph
• Use white space generously
• Start each paragraph with topic sentence

Why: AI processes text more effectively when well-structured. Human reviewers scan faster.

Lead with Strengths

Put your strongest points first in each capability statement:

❌ Weak Opening: "We were founded in 2010 and have grown to 50 employees. We provide project management services using various methodologies."

✅ Strong Opening: "We provide IT project management and PMO services for federal infrastructure projects, having delivered 120 projects totaling $340M with 96% on-time completion rate. Our 18 PMP-certified project managers specialize in Agile, Waterfall, and hybrid methodologies."

Why: The AI and human readers prioritize early content. Lead with impact.

Avoid Marketing Fluff

Focus on facts, not adjectives:

❌ Fluff: "We are a leading provider of innovative, cutting-edge solutions leveraging world-class expertise to deliver exceptional results through best-in-class methodologies."

✅ Facts: "We provide cloud migration services specializing in AWS and Azure. Our team of 25 certified cloud engineers has migrated 3,200 servers across 48 projects totaling $72M, achieving average 38% cost reduction for clients."

Why: The AI can't match against adjectives like "innovative" or "world-class." Procurement officers distrust marketing language. Facts build credibility.

Common Capability Statement Mistakes

Mistake 1: Vague, Generic Statements

Problem: "We provide comprehensive IT services to meet all your technology needs."

Why It Fails:

• No specific services mentioned
• No technology expertise identified
• No quantified experience
• No differentiators

Fix: Break into specific capabilities with details for each (cloud, cybersecurity, development, etc.)

Mistake 2: No Quantification

Problem: "We have extensive experience in project management with a highly qualified team delivering successful projects."

Why It Fails:

• "Extensive" is subjective
• "Highly qualified" is unverifiable
• "Successful" is unmeasured

Fix: "We have managed 85 IT projects totaling $120M with a team of 12 PMP-certified project managers, achieving 94% on-time delivery rate and average customer satisfaction score of 4.6/5.0."

Mistake 3: Mixing Multiple Capabilities

Problem: Single statement trying to cover everything:

"We provide engineering, project management, environmental assessment, IT consulting, and change management services for infrastructure, technology, and policy projects across all sectors using various methodologies and tools with experienced staff."

Why It Fails:

• Too broad to match anything well
• No depth on any capability
• Impossible for AI to extract specific matches

Fix: Create separate capability statements for each service (one for engineering, one for project management, one for environmental, etc.)

Mistake 4: No Supporting Evidence

Problem: "We are experts in blockchain technology and AI/ML solutions."

Supporting Past Performance: (None listed)

Why It Fails:

• Claim without proof
• AI applies credibility penalty
• Procurement officers skeptical

Fix: Either add supporting past performance or remove the capability (or mark as "Emerging" if you're building capability)

Mistake 5: Outdated Technology References

Problem: "We develop web applications using PHP 5, MySQL 4, and jQuery. Our team is experienced with Windows Server 2008 and Internet Explorer 8."

Why It Fails:

• Technologies are 10-15 years outdated
• Signals lack of current expertise
• Doesn't match modern RFP requirements

Fix: Update to current technology stack: "We develop modern web applications using React 18, Node.js 20, and PostgreSQL 15, deployed on containerized cloud infrastructure (Docker, Kubernetes) on AWS and Azure."

Mistake 6: Only Listing Services, Not Capabilities

Problem: Treating capabilities as a service catalog:

• "Project Management"
• "Software Development"
• "Security Assessment"
• "Training"

Why It Fails:

• No detail on HOW you deliver
• No differentiators
• No evidence of expertise
• Impossible for AI to match against specific requirements

Fix: Each line item should be expanded to full capability statement with who, what, how, where, when, why.

Maintaining and Updating Capabilities

When to Update

Immediately:

• New major contract completed (add supporting evidence)
• New certification obtained (link to capability)
• New service offering launched (add emerging capability)
• Technology stack updated (revise tools/platforms mentioned)

Quarterly:

• Update quantified metrics (number of projects, contract values)
• Refresh staff counts and certifications
• Add recent outcomes and results
• Promote emerging capabilities to secondary if evidence built

Annually:

• Comprehensive review and rewrite
• Remove outdated capabilities (discontinued services)
• Consolidate overlapping capability statements
• Refresh all numbers and metrics

Testing Capability Effectiveness

Use Cothon analytics to measure capability statement performance:

Metrics to Track:

Match Rate: How often do opportunities match your capabilities?

• Target: 10-20 relevant matches per week

Confidence Scores: What's the average confidence score for matches?

• Target: 75%+ average confidence

View-to-Bid Conversion: Of matched opportunities, what % do you pursue?

• Target: 15-25% (if too low, matches aren't relevant; if too high, you might be missing opportunities)

Win Rate by Capability: Which capabilities produce the most wins?

• Focus investment on high-win-rate capabilities

Example Analysis:

Capability: Cloud Migration Services

• Match Rate: 8 opportunities/week
• Average Confidence: 88%
• View-to-Bid: 22%
• Win Rate: 35%
• Conclusion: High-performing capability, maintain and expand

Capability: Blockchain Development

• Match Rate: 0.5 opportunities/week
• Average Confidence: 45%
• View-to-Bid: 10%
• Win Rate: 0% (0 wins from 2 bids)
• Conclusion: Underperforming capability, either add evidence or remove

A/B Testing Capability Language

Test different phrasings to optimize match quality:

Original Capability:

"We provide cybersecurity services including assessments and testing."

Metrics: 12 matches/week, 65% average confidence

Revised Capability:

"We provide cybersecurity risk assessment and penetration testing services using NIST 800-53 control framework and OWASP testing methodology. Our team of 8 CISSP-certified security analysts has completed 85 assessments for federal agencies with zero security breaches."

New Metrics: 18 matches/week, 87% average confidence

Result: Increased specificity improved both match volume and confidence.

Advanced Capability Strategies

Strategy 1: Vertical-Specific Capabilities

Instead of generic capabilities, create vertical-specific versions:

Generic Capability:

"We provide custom software development services using Agile methodologies."

Vertical-Specific Capabilities:

Healthcare Vertical:

"We provide custom healthcare software development specializing in Electronic Health Record (EHR) integration, HL7 FHIR interoperability, and PHIPA/PIPEDA privacy compliance. Our team has developed 12 healthcare applications serving 2.5M patient records for provincial health ministries and hospital networks."

Justice Vertical:

"We provide custom justice sector software development specializing in case management systems, evidence management, and court scheduling applications. Our team has developed 8 justice applications for federal and provincial departments including RCMP, Public Prosecution Service Canada, and provincial courts."

Benefit: Much higher match confidence for vertical-specific opportunities (90%+ vs. 60% for generic)

Strategy 2: Teaming Capability Profiles

Create capabilities for partnered offerings:

Structure:

"In partnership with [PARTNER], we provide [COMBINED CAPABILITY]. We contribute [YOUR ROLE] while [PARTNER] provides [THEIR ROLE]. Together we have [COMBINED PAST PERFORMANCE]."

Example:

"In partnership with ABC Environmental (PSAB-certified Indigenous environmental consulting firm), we provide comprehensive infrastructure environmental assessment services. We contribute engineering design and project management while ABC Environmental provides Traditional Ecological Knowledge (TEK) studies, Indigenous community engagement, and environmental monitoring. Together we have completed 18 infrastructure EAs including 6 CEAA panel reviews, with 100% regulatory approval rate and strong Indigenous community support."

Benefit: Qualifies you for larger, multi-discipline opportunities requiring capabilities beyond your core team

Strategy 3: Outcome-Focused Capabilities

Structure capabilities around client outcomes rather than service descriptions:

Service-Focused (typical):

"We provide business process re-engineering using Lean Six Sigma methodology."

Outcome-Focused:

"We help federal agencies reduce program delivery costs and improve citizen satisfaction through business process re-engineering. Our Lean Six Sigma methodology typically delivers:

• 35-50% reduction in process cycle time
• 25-40% decrease in operating costs
• 40-60% improvement in client satisfaction
• 20-35% reduction in error rates

Example: For a provincial benefits program, we reduced application processing time from 45 days to 18 days (60% improvement) while maintaining 99.2% accuracy, enabling $2.3M annual savings."

Benefit: Resonates better with outcome-focused RFP evaluation criteria and executive summaries

Next Steps

Once your capability statements are complete:

FAQ

Q: How long should a capability statement be?

A: Core capabilities: 200-400 words each. Secondary capabilities: 100-200 words. Emerging capabilities: 50-100 words. Quality beats quantity—better to have 5 detailed capabilities than 20 vague ones.

Q: Should I include capabilities I'm building but haven't delivered yet?

A: Yes, but mark them as "Emerging" and be honest about your experience level (e.g., "We are building capability in AI/ML solutions, having completed 2 pilot projects and hired 3 data scientists"). Don't claim full capability without evidence.

Q: Can I copy capability statements from competitors or proposals?

A: Don't copy verbatim (plagiarism), but absolutely study competitor profiles and winning proposals to understand effective structure and language. Adapt the style to your own experience.

Q: How do I write capabilities for entirely new service areas with no past performance?

A: Focus on transferable experience, team credentials, and pilots: "We are launching cloud security architecture services building on our 10-year cybersecurity assessment practice. Our team includes 2 AWS Certified Security Specialists and 4 CISSP-certified consultants, and we've completed 3 pilot cloud security reviews pro bono for non-profit clients."

Q: Should capabilities be written in first person ("we provide") or third person ("XYZ Corp provides")?

A: First person ("we provide") is standard and reads more naturally. Third person sounds stilted. The AI processes both equally.

Q: Do capabilities affect opportunity matching or just proposal generation?

A: Both. The AI uses capabilities to: (1) match opportunities to your profile, (2) score requirements against your fit, (3) generate proposal content. High-quality capabilities improve all three.

Q: Can I write different capability statements for different markets (federal vs. provincial)?

A: Yes. Create market-specific capability profiles or versions that emphasize relevant experience. Example: "Federal Government Healthcare IT" vs. "Provincial Healthcare IT" with different past performance and relevant standards.

Q: What if my capabilities overlap (e.g., "Software Development" and "Application Modernization")?

A: That's fine as long as each statement has distinct focus. "Software Development" might emphasize new applications while "Application Modernization" focuses on legacy migration. Different RFPs will match different statements.

Q: How specific should I be about clients?

A: Name federal departments and provincial ministries (public information). For private clients, use generic descriptions unless you have permission to name them: "Fortune 500 financial institution" instead of "Bank of Montreal."

Q: Should I update capabilities for every completed project?

A: Update metrics quarterly (e.g., "65 projects" becomes "68 projects") but don't rewrite capability statements for every project. Save rewrites for major capability evolution (new technology stack, new methodology, entry into new vertical).