Bluefly Technology Reduction¶
Stop maintaining what you no longer need.
We find custom technology you're still paying to maintain that your existing systems can now replace, prove it can safely go away, and help you remove it.
This file is the canonical definition of the offer. The registry entries in
Engineering-Standard/authority/Portfolio-Registry.yaml (offerings:) point here.
Sales material lives in sales-package.md, delivery in
delivery-method.md, and the shared fields and templates in
delivery-kit.yaml. Nothing else defines this offer.
The offer ladder¶
| Stage | Offer | Customer question it answers | Output |
|---|---|---|---|
| 1. Entry | Maintenance Review | What are we maintaining that we don't need anymore? | Deletion Plan |
| 2. Remediation | Safe Removal | Can we actually turn it off without breaking anything? | Retired systems, verified |
| 3. Recurring | Maintenance Watch | What can we stop maintaining now, and what are we about to build that we shouldn't? | Quarterly two-list report |
Each stage stands alone. A customer can buy a Review and act on the Deletion Plan themselves. Safe Removal is sold against an approved Deletion Plan. Watch is sold to customers who have completed at least one removal, or who already run a standardised platform.
The one success measure¶
What the customer no longer has to own.
We do not measure code produced, developers assigned, tickets completed, agents deployed, or hours consumed. Primary measures, defined in delivery-method.md § Metrics:
CUSTOM_SYSTEMS_RETIREDMAINTENANCE_HOURS_RETURNEDACCESS_POINTS_CLOSEDUPGRADE_TESTING_REMOVEDKEY_PERSON_DEPENDENCIES_REMOVED
Plus ANNUAL_OWNERSHIP_COST_REMOVED only where customer evidence supports it. Every
number carries SOURCE, ASSUMPTION and CUSTOMER_CONFIRMED. We never present an
estimate as a saving.
What it is not¶
- Not a rewrite. We remove things. If the answer is "keep it," we say so.
- Not a platform to buy. The customer's existing platforms are the replacement. No new Bluefly software is required to buy or deliver this offer.
- Not staff augmentation. Scope is a bounded estate, not a headcount.
- Not an AI pitch. How Bluefly delivers is not the value the customer buys.
Commercial classification (internal)¶
| Item | Class |
|---|---|
| Bluefly Technology Reduction | COMMERCIAL_OFFER (offer family) |
| Maintenance Review | COMMERCIAL_OFFER / entry engagement |
| Safe Removal | SERVICE / remediation engagement |
| Maintenance Watch | RECURRING_COMMERCIAL_OFFER |
| ContextControl | Separate flagship product. Not required to sell or deliver this offer. It may later carry delivery evidence or customer visibility. |
| Bluefly delivery tooling | Implementation substrate. Never part of the customer-facing value proposition. |
Pricing basis¶
No price is set here: there is no canonical Bluefly pricing evidence for this offer yet. The unit is fixed so pricing can be set once and quoted consistently:
- Maintenance Review: fixed fee per bounded estate. The scope unit is one of: a number of sites, a number of applications, a number of repositories, one platform family, one business unit, or one digital estate. Never hourly.
- Safe Removal: fixed fee per approved Deletion Plan item, or per batch of items, sized
by the
REMOVAL_EFFORTandREMOVAL_RISKalready recorded in the plan. - Maintenance Watch: recurring quarterly fee per estate under watch.
Full engagement scope, inclusions and exclusions: delivery-method.md § Commercial scope.