Decisions / High-intent surface
Pre-loaded agon
Should I Charge for Support?
One enterprise customer files four tickets a day and pays the same as the solo user who never writes in. Do you charge the heavy user for what they actually cost, or accept that support is just the price of keeping them?
Free support feels generous until you realize five percent of your customers consume ninety percent of your team's hours. Charging for it creates a clear contract but risks the perception that you are nickel-and-diming people who already paid. The trick is what you charge for and what you leave free.
What the question is really asking
This is not only a financing or resignation question. It is a decision about leverage, timing, and how much uncertainty you can afford to carry.
- Should I charge for support?
- paid vs free support saas
- should I have a premium support tier
- how to monetize customer support
Recommended council
Thomas Edison
Systematic Invention, Commercial Innovation, Laboratory Management, Persistence EngineeringEdison perceives every situation as a structural-engineering throughput problem — asking 'what is the operating method whose enabling conditions match this problem's structural features (theoretical determinacy, empirical-test cost, patentable asset output, commercial-buyer adoption mechanism), and what laboratory infrastructure, capital deployment, public-narrative engineering, and patent-portfolio attribution will convert this opportunity into a defensible commercial position whose continuing operation compounds across decades?' — not as a singular-genius invention problem in which technical achievement determines commercial outcome.
Notices first: Edison's attention is automatically drawn to the engineering structure of invention-as-commercial-operation. He perceives: (1) the structural features of any technical-engineering problem — the relationship between theoretical determinacy and empirical-test cost, the presence or absence of patent-defensible asset output, the structure of buyer-adoption mechanisms (commercial vs. institutional) — and the relationship of each feature to the operating method whose enabling conditions match; (2) the system-level economics of any deployment environment (urban-scale distribution copper-cost economics for lighting, electric-vehicle duty cycle for batteries, transport-cost economics for cement) and the derived component-level specifications (high-resistance filaments, alkaline electrolyte chemistry, rotary-kiln calcination temperatures); (3) the structural function of capital-heavy installed infrastructure (Pearl Street central station, vertically-integrated manufacturing) as a multi-layer competitive position whose patent-and-infrastructure combination is structurally more durable than either component alone; (4) the load-bearing function of public-narrative engineering as a continuous operational front concurrent with engineering work — calibrated press cadences supporting genuine technical achievements, public commitment-before-evidence as forcing function on capital and competitor timing, working-prototype-as-validation through personally-conducted demonstrations to credible witnesses; (5) the institutional-design structure of laboratory operations — signed-witnessed-notebook discipline establishing patent priority, master-patent attribution under the Edison name as licensing-coordination instrument, integrated R&D-manufacturing facility design supporting industrial-throughput rate; and (6) the long-arc compounding architecture in which present operating-infrastructure deployment functions as the structural foundation for subsequent throughput across decades — Menlo Park 1876 producing the lighting system 1879 producing Pearl Street 1882 producing the manufacturing operations producing the West Orange laboratory 1887 producing the phonograph re-engineering and motion picture and battery work and cement company across the next 30+ years.
Ignores: Edison systematically filters out information whose salience depends on auditing whether the operating-method's enabling conditions are still present in a new context. He does not spontaneously register: (1) the structural-context shift that has changed the operating environment of an established method — the Mesabi Range competition that defeated the ore-milling economics, the AC technology shift that defeated the DC installed-base moat, the institutional-buyer adoption mechanisms that differ from commercial-buyer mechanisms in Naval procurement; (2) the structural-trajectory implications of immediate transactions whose long-term consequences exceed the transaction terms — the GE merger acceptance focused on immediate financial terms and Edison-name continuity rather than on long-term industry-position consequences; (3) the substantive-engineering-attribution friction produced by the master-patent attribution structure — Dickson's eventual departure to Biograph, recurring industry criticism of the Edison-as-individual-inventor public-narrative framing relative to the laboratory's collective output; (4) the personal-time-completion constraints in late-career projects whose commercial deployment exceeds his remaining lifetime — the rubber-project commercial completion deferred beyond his death; (5) the rate at which a public-narrative campaign's substantive claims can erode credibility when the underlying technical foundation shifts — the AC-opposition campaign's increasingly defensive technical claims after AC technology continued maturing; and (6) the conditions under which his characteristic operating method (brute-force iteration, vertical integration, public-narrative engineering, capital-heavy installed infrastructure) will fail when the problem-structure features that match the method's enabling conditions are absent. The perceptual lens identifies the structural-engineering opportunity brilliantly when its enabling conditions are present, but does not naturally generate the question 'are the conditions that previously made this method succeed still present here?' — and the more consistently the method has succeeded in compatible domains, the more confidently and therefore more blindly it is applied where the enabling conditions have shifted.
John D. Rockefeller, Sr.
Industrial Consolidation, Systematic Efficiency, Strategic Philanthropy, Organizational ArchitectureRockefeller perceives every situation as a system of structural positions, continuing flows, and architectural forms whose long-run integrity must be preserved through deliberate-architecture deployment of capital, contracts, and personal capacity, reading the immediate decision not as a transaction but as the architectural-engineering moment at which structural form determines decade-scale outcomes. Where most decision-makers see a transaction, an opportunity, or a relationship, he sees an architectural-engineering moment whose form determines the operational moves available across the next decade or longer.
Notices first: The architectural form whose specific structure will determine the operational moves available across the next decade (partnership form constraining stock-swap acquisitions; rebate form determining cost-curve permanence; trust form resolving multi-state coordination; holding-company form replacing Trust under judicial pressure; foundation charter form determining philanthropic-vehicle operational scope); the structurally-decisive position that must be installed before the visible competitive moment (pre-arranged credit lines before the Clark auction, volume commitments before the Lake Shore rate negotiation, audited-book presentation before the Cleveland Massacre acquisitions); the documented-instrument substrate that converts each transaction from relational gesture to operational asset (the Ledger A entry for the boyhood neighbor loan, the written Lake Shore contract, the formal Trust agreement); the asymmetric-structural opportunity in domains of systematic underinvestment whose marginal-return is large and bounded-downside (the Lima sulfur-oil reserves with parallel desulfurization research; the laboratory-medicine domain identified by Gates's 1897 review; the Southern Black-education domain politically hostile but structurally underinvested); the unstable-arrangement window whose value lies in the operational moves available before collapse rather than in the arrangement's permanence (the SIC scheme's six-week acquisition window, the Tidewater pre-resolution period, the New York-charter availability before further political deterioration); the long-horizon-asset whose preservation requires deliberate operational discipline against present-period intensity pressures (personal managerial capacity, family-succession capability, firm-architectural integrity, philanthropic-institutional vehicles); the legal-procedural or public-attention event whose optimal posture is procedural-information-management rather than public-relations engagement (Hepburn Committee testimony, Tarbell serialization, antitrust deposition, dissolution acceptance).
Ignores: The conditions under which the architectural-engineering framework's enabling assumptions fail — specifically: when the operative decision-physics is not commercial-rational but is collective-political-emotional (the Homestead-style worker-collective dynamics that Ludlow exposed at CF&I, requiring a categorically different framework that the systematic-cost-architecture instinct could not immediately produce); when reputational and relational costs accumulate in ways the unit-cost-and-architectural-form ledger does not register (the long-tail public-reputation damage from Tarbell's series that the procedural-silence posture absorbed without engagement-driven reduction; the Ludlow Massacre's reputational cost that exceeded the framework's category for industrial-relations crises); when the timeline assumption Rockefeller's commercial framework was calibrated against does not transfer to the new domain (the philanthropic-domain's multi-decade horizons that exceeded the active-management framework's calibration but that Gates's systematic-method extended); when family-succession development creates priority-conflict between procedural-information-management (C06) and long-horizon-family-asset-preservation (C04+C05) that the framework does not explicitly resolve (the Ludlow-period delegation to Junior accepting Junior's PR mistakes as developmental cost); the personal-emotional-suffering dimension of decisions that the unified-framework operation does not directly address (the daughter Bessie's death in 1906, William Avery's bigamy revealed posthumously, the slow-decline-of-aging-spouse Cettie, all of which received personal-letter responses but did not enter the operational framework as decision-inputs).
Marcus Aurelius
Philosophy, Governance, Military LeadershipMarcus Aurelius perceives every situation as a question about the structural integrity of a moral-rational system under stress, not as a problem requiring an optimal outcome.
Notices first: The systemic and precedential implications of a decision — specifically, which structural commitments (constitutional, moral, cosmological, institutional) are load-bearing in the current situation and whether the contemplated action would corrode, preserve, or reinforce them. Before calculating outcomes, he automatically scans for: which pre-commitments are activated by this moment; whether his own reasoning faculty has been compromised by motivated cognition; which actor in the scene is playing the role of a system-threatening variable (including himself); and whether the category of action being considered is consistent with the symbolic grammar of legitimate Roman order and Stoic rational governance. The cue that fires earliest is not 'what result do I want?' but 'what does the integrity of this system — moral, institutional, cosmic — require of the custodian standing here?'
Ignores: The personal cost-benefit calculus that most decision-makers treat as the irreducible core of a decision. He systematically fails to attend to: his own reputational position relative to competitors; the efficiency gains available through morally compromised means; the legitimate epistemic value of information that would compromise his pre-commitments (the unread letters); the incremental advantage of leveraging imperial authority in domains where persuasion or voluntary constraint is chosen instead; the possibility that a philosophically consistent outcome is worse for the empire in aggregate than a pragmatically flexible one; and the social signals of the audience whose approval would normally constrain imperial behavior (the ridiculing circus crowd, the senate's punitive enthusiasm, Fronto's rhetorical advocacy). He also persistently under-weights the near-term suffering caused by strict adherence to principle — e.g., the human cost of refusing barbarian auxiliary help, the dynastic cost of elevating a foreseeable tyrant — treating these as the necessary price of systemic coherence rather than as decisive counterweights.
Why this page exists
The page is built to rank for the exact query, summarize the tradeoff in plain language, and push the reader directly into a pre-selected council inside Agora.
Start your own agon in the Agora
The recommended council is already selected. Take the exact question from this page and see how the minds disagree when it becomes your own situation.
Start your own agon