Narrow scope beats vague coverage
83(b) Desk is useful only when the facts match the supported workflow. The product says no before it stretches into advice.
Back to 83(b) Election Desk
About the product
Built for the founder who already decided, not for the decision itself.
83(b) Election Desk exists because the 30-day filing window is operationally unforgiving, while the decision to file remains a legal and tax judgment outside a software packet.
The story
Self-preparation, with a smaller promise.
The product starts after the user has already decided to file. It does not weigh tax upside, forfeiture risk, valuation, securities law, immigration facts, or grant eligibility.
The useful part to systematize is the packet: transfer-date deadline, Form 15620 field checklist, company copy letter, mailing proof, and a passport record that makes the evidence easy to review.
If the user asks whether to file, what value to use, whether a transfer occurred, or how to fix a late election, the product should stop clearly instead of pretending the answer is a form field.
Us vs the old way
The difference is the boundary.
The product is not trying to imitate a full-service firm. It is trying to make the repeatable part of a narrow filing workflow clearer, faster, and easier to review.
| The usual route | Our lane |
|---|---|
| Search for 83(b) templates and hope the deadline, copies, and proof are handled. | Start with a deadline and hard-stop gate before packet assembly. |
| Mix should-I-file advice with operational filing logistics. | Only organize the packet after the user already decided to file. |
| Store sensitive identity facts in random drafts. | Avoid collecting full SSNs/TINs and remind the user to complete them on the official form. |
| Treat late, RSU, unexercised-option, and revocation cases like normal packets. | Stop those cases before checkout. |
Official sources beat memory
Deadlines, method rules, and filing limits are tied back to government sources, with review dates shown in the product.
Local drafts beat account lock-in
The working pattern is no account by default, browser-saved drafts, a one-shot software fee, and a reusable annual passport.
A packet is not representation
The user reviews, signs, files, and pays through the official channel unless a future service explicitly says otherwise.
Publisher
Yann Lephay
Independent software maker and publisher
Builder of narrow self-preparation software for recurring compliance paperwork: official sources first, local drafts, public limits, and no account lock-in.
The same operating pattern that shaped LMNP Facile is used here: publish the limits, cite the official sources, keep drafts local, charge once, and stop before software pretends to give individualized professional advice.