The HARBOR Framework.
Six stages to transform government contracting services into scalable products that succeed in the federal market.
The shape of the work.
The stages are sequential, but the work is not a waterfall. Each one produces an artifact the next one needs.
Harvest
What products are hiding in your work?
Architect
Which product first?
Risk-Proof
Can we afford the trust infrastructure?
Build
How do we make it repeatable?
Operate
How do we defend what we built?
Replicate
How do we scale?
The six stages.
Harvest
What products are hiding in your work?Identify your product in the work you already do and test service-to-product fit. Not every service becomes a product. The ones that do share patterns: repeatability, clear boundaries, and customers willing to pay for the thing rather than the hours.
- Contract archaeology across active and completed contracts
- IP inventory creation and classification
- Service-to-Product Fit scoring across six dimensions
- Candidate shortlisting for Architect
Architect
Which product first?Choose the right hill to take first. Concentration beats diversification in federal productization. One product pursued with full resources beats three products pursued with split attention.
- Hill Selection Matrix for evaluating candidates
- Resource allocation and concentration strategy
- Three-customer validation threshold before product two
- Product commitment and validation roadmap
Risk-Proof
Can we afford the trust infrastructure?Build trust through compliance, authorization, and survivable architecture. Compliance is not a phase you complete; it is an operating discipline you maintain.
- Compliance as operating discipline
- FedRAMP and CMMC authorization pathway selection
- Architecture for survivability and monitoring
- Authorization economics and sponsor strategy
Build
How do we make it repeatable?Create repeatability through codification and standardization. Turn expertise into artifacts. Decide what gets standardized and what stays configurable.
- Codification of tacit expertise into artifacts
- The 70/30 principle: standardized core, configurable surface
- Decision trees, templates and training materials
- Configuration versus customization boundaries
Operate
How do we defend what we built?Defend product boundaries against scope creep. The product that tries to be everything becomes nothing. Define clear boundary zones and build the framework for saying no constructively.
- Four boundary zones: core, configurable, optional, excluded
- Boundary defense against scope-creep requests
- ATO boundary alignment with product boundaries
- CLIN structure reinforcing product boundaries
Replicate
How do we scale?Scale through pricing and acquisition mechanics. Price value instead of hours. Structure CLINs and vehicles that make your product purchasable.
- Value-based pricing models for federal products
- CLIN structure design
- Vehicle strategy: GSA MAS, OASIS+, OTA, SEWP
- Defensible value justification for proposals
Before stage one
Should we productize?
The free HARBOR Signal is the phase-zero answer. Thirty questions across five dimensions, a go or no-go verdict, and no account required.
- Services Business Health Diagnostic across five dimensions
- Five Filters Reality Check: five conjunctive go/no-go filters
- Builder-Operator Assessment across seven capabilities
- Overall verdict: Proceed, Proceed with conditions, or Not Yet
Start with the free read.
The Signal scores where the firm is and points at the next useful step. It takes about eight minutes and needs no account.