Choose what to get done
Compute the break-even sales change for a price change
You get the minimum percent (and unit) sales-volume change at which a proposed price change leaves total profit contribution unchanged.
Compute the dilution impact of a pre-money option pool top-up
A function that computes the effective (pool-adjusted) price per share and the share of dilution borne by existing holders when a new option pool is created on a pre-money basis.
Core-capability gap register
A structured register comparing required capabilities to current capabilities, flagging each gap with a fill strategy.
Customer lifetime value (simple and discounted)
The customer lifetime in years, the simple LTV, and the discount-adjusted LTV you can put against CAC.
Customer profile
A ranked customer profile for one segment: the jobs your customer is trying to get done, the pains in their way, and the gains they want, every entry carrying a high, medium, or low rank so the profile states priorities instead of listing everything equally.
Cyclomatic complexity with refactor flags
McCabe cyclomatic complexity per function from its control-flow graph, with a refactor flag for any that exceed your threshold.
Defect density per module with ranked hotspots
Defect density per module against your chosen size unit, the overall density, and a ranking of the most defect-dense modules.
Defect removal efficiency
Defect Removal Efficiency from pre-delivery vs escaped defect counts, with an optional per-phase breakdown.
Demand-gen lead-stage definition register
The buyer gets a register where each required lead stage (e.g. MCL, MEL, MQL, SQL) has a definition, a funnel phase, an owning team, an entry criterion, and a lead-score threshold, with thresholds increasing down the funnel.
Deploy pipeline and hosting
The app is deployed and the health endpoint returns 200.
Deploy runbook with rollback
An ordered, role-assigned deploy runbook with preflight checks, deploy steps, verification, and a rollback path that every failure step routes to.
Design a Good-Better-Best SaaS package structure
I get a clean Good-Better-Best tier table where every feature is placed once, each tier targets a distinct segment, and higher tiers strictly contain lower-tier features (monotonic gradation).