Engineering Methodology
Snapshot basis
3 published app inventories using PHP snapshots generated on March 5, 2026.
Consistent model
Every app uses the same point logic, hours-per-point assumption, blended rate, and rounding method before product-specific adjustments are applied.
Clear boundary
This page supports diligence and ownership review with rebuild-value math. It is not the live subscription pricing path, a product-tour substitute, or an investor valuation page.
Build-cost methodology behind current HospiEdge rebuild values.
Use this page after the main Engineering review to verify how the published rebuild references were derived and what comes from dated PHP inventory snapshots before the conversation moves into a narrower commercial or proof lane.
- Best for: methodology checks, scope assumptions, and ownership-oriented rebuild logic after product-fit and engineering review are already underway.
- Go elsewhere for: the normal platform buying path, live workflow proof, or first-touch product education.
What to verify in this review
Use this section to confirm the formula inputs, the judgment layer, and whether the review should stay on methodology or move to a more specific next owner.
See the actual formula, the current PHP inventory inputs, and the app-specific multipliers behind the published rebuild ranges without confusing them with the live platform price.
File count, function count, and PHP line count come from generated inventory snapshots. Low-case and high-case numbers are explained through named scope adjustments under each app instead of being hidden inside a broad estimate.
Use this page for the methodology check, then switch lanes only when the next question changes: Pricing for the live platform route, Engineering for license context, Products or Finance for operating proof, and Contact for a scoped follow-up.
Total PHP files across the published inventories used on this page.
Named PHP functions counted across the current published app inventories.
PHP lines represented in the inventories used for the current worksheet math.
Important context before you read the numbers
These numbers explain rebuild-value math after a diligence review starts. They are separate from subscription pricing, company valuation, and first-touch product education.
These estimates model what it could cost to recreate the software scope shown in current inventories, not what a buyer must subscribe to in order to start using HospiEdge today.
These figures are not a direct valuation of HospiEdge. Read them as methodology behind ownership-oriented rebuild-value references and diligence conversations.
The live platform route remains separate: Launch Partner pricing is $279/month or $2,899/year for 1 account, $749/month or $7,799/year for 3 accounts, and $2,190/month or $22,999/year for 10 accounts. AI is included in every platform plan, Scheduling is included with the active platform account, and the connected platform path can extend into HETable, POS, Hospi Label, Reader, training, and setup assistance where appropriate. Use this page only when the question has shifted from buying access to validating rebuild-value support.
What a diligence-heavy buyer can confirm here
Use this section to keep the methodology review concrete, traceable, and honest about where estimate judgment enters once the conversation moves beyond basic product-fit questions.
Snapshot traceability stays visible
Each worksheet keeps the source counts visible so a buyer can see the published values are tied to a dated inventory basis instead of generic market claims.
The core formula stays consistent
Every app uses the same point model, hours-per-point assumption, blended rate, and rounding approach. Only the complexity multiplier and scope adjustments change by product.
The judgment layer is named, not hidden
Low-case and high-case ranges are built from explicit adjustment rows so buyers can see where implementation scope, integration depth, and compliance demands widen or narrow the estimate.
Workflow proof still happens elsewhere
This page validates the math only. Workflow proof still belongs on the live product pages, with Finance added when accounting-path proof matters.
Published Rebuild Values (Current)
These are the values shown across product and engineering pages for the apps with published inventory snapshots and are recalculated from the formula below.
Low: $350,000
Midpoint: $420,000
High: $900,000
Low: $600,000
Midpoint: $880,000
High: $1,800,000
Low: $450,000
Midpoint: $760,000
High: $1,100,000
Formula used across the published apps
Every published app uses the same equation. The main product-specific variable is the complexity multiplier.
1) Engineering Points
Points = files x 1 + functions x 0.5 + PHP lines / 100
2) Base Hours
Base hours = points x 5.0
3) Complexity Hours
Complexity hours = base hours x app multiplier
4) Midpoint Cost
Cost = complexity hours x $160/hour, then rounded to nearest $10k
| Input | Value | What it captures |
|---|---|---|
| PHP file count | Direct from inventory snapshot | Represents route and module surface area that must be rebuilt and tested. |
| Named function count | Direct from inventory snapshot | Represents business logic units that carry behavior and branching complexity. |
| PHP line count | Direct from inventory snapshot | Captures implementation depth and integration glue that files/functions alone miss. |
| Complexity multiplier | App-specific coefficient | Adjusts for real-world difficulty: workflow coupling, integrations, compliance, and launch risk. |
| Blended hourly rate | $160/hr | Weighted average of product engineering, QA, and release management effort. |
Per-App worksheet (exact math)
Each row ties the midpoint and range logic to inventory counts and named scope adjustments for that app.
HospiEdge Scheduling
Snapshot source: 93 files,
243 functions,
21,784 lines.
| Step | Formula | Result |
|---|---|---|
| Engineering points | 93 + (243 x 0.5) + (21784 / 100) | 432.34 points |
| Base rebuild hours | 432.34 x 5.0 | 2,161.7 hours |
| Complexity-adjusted hours | 2,161.7 x 1.21 | 2,615.7 hours |
| Raw midpoint cost | 2,615.7 x $160 | $418,505 |
| Rounded midpoint from formula | round(raw midpoint / 10,000) x 10,000 | $420,000 |
| Published midpoint | Matches current product and engineering pages | $420,000 |
Low-case scope path
- Single-location launch using existing templates -$35,000
- Minimal integration profile (light POS/payroll touchpoints) -$20,000
- Reduced policy matrix and lower QA depth -$15,000
$420,000 + -$70,000 = $350,000
High-case scope path
- Enterprise labor forecast automation and scenario planning +$130,000
- Multi-brand rule matrix with location-specific policy packs +$120,000
- Deep payroll and POS connector hardening +$90,000
- Advanced notification and workflow automation +$70,000
- Data migration, parallel run, and implementation support +$70,000
$420,000 + +$480,000 = $900,000
HospiEdge Operations
Snapshot source: 187 files,
321 functions,
26,190 lines.
| Step | Formula | Result |
|---|---|---|
| Engineering points | 187 + (321 x 0.5) + (26190 / 100) | 609.40 points |
| Base rebuild hours | 609.40 x 5.0 | 3,047.0 hours |
| Complexity-adjusted hours | 3,047.0 x 1.81 | 5,515.1 hours |
| Raw midpoint cost | 5,515.1 x $160 | $882,411 |
| Rounded midpoint from formula | round(raw midpoint / 10,000) x 10,000 | $880,000 |
| Published midpoint | Matches current product and engineering pages | $880,000 |
Low-case scope path
- No advanced AI coaching or incident enrichment -$95,000
- Single-brand deployment with simplified multi-location controls -$80,000
- Standard integration profile without custom POS adapters -$55,000
- Lean reporting and reduced compliance hardening -$50,000
$880,000 + -$280,000 = $600,000
High-case scope path
- Multi-brand architecture with strict tenant separation controls +$280,000
- Compliance hardening and enterprise-grade audit governance +$220,000
- Deeper POS and financial system integration program +$180,000
- AI image and advisor expansion with review loops +$140,000
- Security, release, and reliability controls for enterprise operations +$100,000
$880,000 + +$920,000 = $1,800,000
Hospi Edge Table
Snapshot source: 136 files,
597 functions,
36,732 lines.
| Step | Formula | Result |
|---|---|---|
| Engineering points | 136 + (597 x 0.5) + (36732 / 100) | 801.82 points |
| Base rebuild hours | 801.82 x 5.0 | 4,009.1 hours |
| Complexity-adjusted hours | 4,009.1 x 1.18 | 4,730.7 hours |
| Raw midpoint cost | 4,730.7 x $160 | $756,918 |
| Rounded midpoint from formula | round(raw midpoint / 10,000) x 10,000 | $760,000 |
| Published midpoint | Matches current product and engineering pages | $760,000 |
Low-case scope path
- Single-floor host board with no kiosk channel launch -$130,000
- Manual section balancing instead of full smart assignment tuning -$70,000
- Basic API and webhook footprint -$50,000
- Light analytics and reporting scope -$60,000
$760,000 + -$310,000 = $450,000
High-case scope path
- Multi-floor and multi-location orchestration +$120,000
- High-volume reservation and waitlist scaling controls +$90,000
- Full kiosk self-seat launch plus assignment explainability +$70,000
- Advanced API security, webhooks, and partner integration support +$60,000
$760,000 + +$340,000 = $1,100,000
Take the next step that matches the decision
Choose one next owner based on the open question: Engineering for implementation or lifetime-license context, the product pages for workflow proof, Finance for accounting-path proof, Pricing for the live platform buying route, or Contact for a scoped follow-through conversation.
Go back to the Engineering page and review the lifetime licensing section before turning the methodology discussion into ownership review.
Return to the app pages and live routes, adding Finance when accounting flow matters, so the methodology review stays tied to actual operating behavior.
Use Pricing for the current Launch Partner route first, then Contact only if the review needs a scoped follow-up: $279/month or $2,899/year for 1 account, $749/month or $7,799/year for 3 accounts, and $2,190/month or $22,999/year for 10 accounts. That remains the live commercial path even when this page appears in the diligence packet.