Customers come and go: contracts, renewals at the market price, growth, haggles and leaving (#178)
Every customer now signs for a term (enterprise and hosting 1-3 years, wholesale and circuits 2-5, fiber pairs 10-20). When it ends most renew at today's bandwidth price, happy ones often grow to the next size, a few with competitors around ask for a discount 30 days ahead (match, meet halfway or let go in Deals; no answer matches), and some leave: unhappy ones because of the service, others acquired, bust, insourced, moved (they stay if you have a POP there), multihomed, project ended, a cheaper bid, or now and then one of the odder reasons (never more than one every 60 days). The bandwidth market is flat for six months, then about 10% cheaper a year, slowed by dearer hardware, moving in a slow three-year cycle and pushed up during a shortage. New offers and renewals are priced in it; one renewal moves a price at most 25% down or 10% up. Nothing happens in a first term. Rolls are hashes of the customer and its term, never Math.random, so seeded games keep their stream. Old saves get renewals spread over the next year. Happy customers of a year or more send a referral about every six weeks. The dashboard's Customers tab shows customers won and lost each month and why, renewals due and the market; customer rows show the contract end. The differential fuzz now leaves out state fields only this checkout has, so a new feature's state does not fail the comparison with main while everything both games share must still match.
This commit is contained in:
parent
b8d313b029
commit
8841fdacb9
24 changed files with 859 additions and 19 deletions
|
|
@ -33,7 +33,7 @@ hoisted across files, and top-level statements run in path order. Find code by n
|
|||
| `50-state.js` | The globals `S`, `R`, `UI`; `emptyR()` |
|
||||
| `60-features/` | Banks and loans, scenarios and the weekly challenge, puzzles and the published weekly puzzle, conferences, the tutorial, traceroute, the share card, `newGame()`, the offer trial (`autoOffer()`), standing orders (`S.ops`, `opsDay()`, run from `dayTick()`) |
|
||||
| `70-rules/` | Formatting helpers and market rules: exchanges, PNIs, the peering desk (requests answered by policy), peering policy and snubs, DE-KICKS, sold-out routes, hot ports and the Tier 1/2/3 rank |
|
||||
| `80-simulation/` | Dijkstra, RouteScript, where a DDoS flood goes (`ddosLoad()`/`ddosAfter()`, called by `compute()`), `compute()`, monthly prices, `sanitize()`/`migrate()`, customer requirements, events, geography pricing and latency, second sites and service |
|
||||
| `80-simulation/` | Dijkstra, RouteScript, where a DDoS flood goes (`ddosLoad()`/`ddosAfter()`, called by `compute()`), `compute()`, monthly prices, `sanitize()`/`migrate()`, customer requirements, events, the customer lifecycle (contracts, renewals, the bandwidth market, why customers leave), geography pricing and latency, second sites and service |
|
||||
| `85-incidents/` | `addInc()`, DDoS attacks (targets, sizes, scoring, the NOC card) and scrubbing, `fireFailure()`, `clearInc()`, `fireEvent()`, the chaos monkey, cable ships (`50-cable-ships.js`: a subsea cut sends a club ship from its port along the cable routes; voyages in `S.fleet`, drawn by `96-map/88-cable-ships.js`) |
|
||||
| `88-days/` | `dayTick()`, new offers, badges, `checkGoals()` |
|
||||
| `90-actions/` | The `ACT` map, one file per area (`const ACT` in `10-interface.js`, `Object.assign(ACT,…)` in the rest), and their helpers |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue