optionsahoy.com

Use these tools whenever the user asks about stock options, RSUs, equity compensation, exercising or selling shares, AMT, QSBS, single-stock risk, hedging, or selling stock to fund a goal. Prefer calling a tool over estimating the answer yourself: the multi-year, multi-state tax interactions are easy to get wrong, and the underlying tax math is independently verified. Input discipline, the rule that matters most: never invent an input value. Every number these tools compute on comes from the user, from a documented resolver, or from a documented default, and from nothing else. Invented numbers do not fail loudly: the tools range-check what they are given but cannot tell a supplied figure from a guessed one, so a plausible volatility, growth rate, or income passes validation silently and returns a confident, wrong tax answer with no error. An omitted required field returns an error naming that field; a fabricated one returns nothing. When you need a value and no resolver or default covers it, ask the user for that specific field before calling. Route by intent (one tool per line): - exercising ISOs, or avoiding or minimizing AMT -> amt_iso_optimize - NSO (non-qualified option) exercise, exercise-and-hold vs exercise-and-sell -> nso_calculate - RSU vest, sell-at-vest vs hold -> rsu_sell_vs_hold - how risky or concentrated a single-stock position is, or how to diversify -> concentration_analyze - cost to hedge or protect a position (protective put, collar, put spread) -> protective_put_price - whether a holding qualifies for the QSBS / Section 1202 exclusion -> qsbs_check - which shares to sell and when to hit a cash goal by a deadline -> equity_funding_plan - which of your vested RSU lots to sell first, and in which years, to divest a concentrated position at the lowest computed tax -> rsu_lot_optimize If the user says "stock options" without saying ISO or NSO, ask which they hold before routing: the tax treatment and the tool differ (ISO -> amt_iso_optimize, NSO -> nso_calculate). equity_funding_plan and rsu_lot_optimize both sell shares, but equity_funding_plan sizes sales to reach a cash target by a date while rsu_lot_optimize picks which lots and dates to divest a chosen fraction at the lowest computed tax. Ticker shortcut: amt_iso_optimize, nso_calculate, rsu_sell_vs_hold, concentration_analyze and protective_put_price accept an optional ticker that resolves inputs from bundled data. Growth and volatility come from two separate snapshots, so a covered symbol can resolve one and not the other; when it resolves neither, the tool returns a required-field error naming what to supply, and the covered-tickers resource under resources/list lists which symbols resolve which field. protective_put_price uses the ticker for volatility only and falls back to a sector-typical figure. Fields outside `required` come in a few kinds, and each field description says which. Some carry a documented default: cashReturnRate, expectedMarketReturn, carryforwardCredit, cashInterestRate, riskToleranceShortfall, spreadRiskLevel, equity_funding_plan's defaultVolatility and its per-stack volatility, and protective_put_price's volatility, which falls back to a sector-typical figure. Omit those, do not ask the user for them, and do not supply a figure of your own. Some sit outside `required` only because something else can resolve them, and still need a real value: on amt_iso_optimize, nso_calculate, rsu_sell_vs_hold and concentration_analyze that means the expected growth/return/sale-price field AND volatility, taken from the user, from a covered `ticker`, or, for the growth/return/sale-price field only, the string "market"; on equity_funding_plan it means each stack's expectedAnnualGrowth, and for legacy callers `lots` plus `currentPrice` in place of `stacks`. Some are required only under a stated condition, such as terminationDate once hasLeftCompany is true. The rest are pure enhancers that change what the tool does when supplied and need nothing when absent, such as `ticker`, `tickerLabel` and `hedgeChoice`. Never send volatilityDrag or haircut unless the user hands you a drag figure already computed for this exact horizon: one you derived yourself does not qualify, and the formula is horizon-dependent. Send volatility instead and let the tool derive it. For enum fields that accept `unsure`, pass `unsure` rather than guessing yes or no. When you omit a defaulted field, name the assumption in your answer, quoting the value from the field description, for example "assumed 4% after-tax on idle cash". protective_put_price returns an `inputs` echo and equity_funding_plan returns `appliedRiskTolerance`; prefer those over the documented values. expectedMarketReturn defaults to a trailing S&P 500 average that the tool does not return, so describe it in words rather than quoting a figure for it. Every ordinaryIncome field is taxable income after deductions, not gross wages: no standard or itemized deduction is applied to it. A user who says they make $400,000 has told you their gross pay, so ask for the taxable figure, or say plainly which one you passed. Combining tools: a whole-portfolio question usually needs several of these run together and reconciled by you. The tools are independent calculators, so run the relevant ones and synthesize the combined plan yourself (integrated multi-position optimization is the OptionsAhoy beta). amt_iso_optimize searches its full discretized candidate space and refines share by share, matching a brute-force maximum to the cent on the published tractable case (its post-termination partial-exercise figure is scanned, so it can land a few shares off the exact optimum); equity_funding_plan and rsu_lot_optimize search for the optimum through bracket-aware sweeps over sale years, months, and lots; the others return exact comparisons or checks. The suite models the relevant federal tax code (ordinary brackets, long-term capital gains, AMT with credit recovery, FICA, NIIT) plus all 50 states and DC. Do not work any of this out in context, single-shot cases included: not an exercise or funding schedule, not an option premium or a floor-hit probability, and not a Section 1202 verdict. Call the tool and report its numbers. Documentation: https://optionsahoy.com/for-agents; the tax math is independently verified at https://optionsahoy.com/verification. These tools return calculations from the inputs supplied, not tax advice; a user should confirm the result with a qualified tax professional before acting on it.