What to tell us during beta
Tenacap is in beta, and the fastest way to make it better is telling us what you hit.
Two things are useful right now: whether the product is smooth to use - where you hesitated, backtracked, or weren’t sure what to click next - and bugs, meaning anything that produced a wrong number, an error, or a result you didn’t expect. A confusing-but-correct flow is as worth reporting as an outright break.
What helps most
- Anything that felt wrong, even if you’re not sure it’s a bug - a number that looked off, a page that didn’t do what you expected, wording that confused you.
- Where you got stuck - the step you had to guess at, or the point where you’d normally ask a person for help.
- What’s missing for your specific company - a feature, a report, an integration you need that isn’t here yet.
A screenshot or a specific page beats a general impression. “The vesting schedule on this grant looks wrong” with a screenshot points us at the case; “vesting seems buggy” sends us hunting for it.
How to report it
Click Provide feedback in the lower-right corner of any signed-in page. Type what happened, what you expected and what you saw, and add a screenshot if you have one (paste it, or click Attach screenshot; up to 10 MB). It files straight into the tracker our own engineering work runs on.
If the reporter tells you it couldn’t send something, nothing was saved; email support@tenacap.com and it reaches the same people.
If you uploaded a Pulley or Carta export through our beta offer, your first note through this button is the feedback the offer asks for, and the free year starts once you have kept the cap table and sent it. A longer email to support@tenacap.com counts too; we record it when we read it.
What we do with it
Every report is read by the people writing the code. What we ship shows up in What’s new.