What to tell us during beta
Tenacap is in beta, and the fastest way to make it better is telling us what you hit. Here's what's most useful to report, and where it goes.
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. Both matter equally; 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 is something we can act on same-day; “vesting seems buggy” usually sends us hunting for the actual case.
How to report it
Use the feedback button in the lower-right corner of any signed-in page — it takes free text and, optionally, a pasted or attached screenshot, and it files directly into the same tracker our own engineering work runs on. There’s no separate form to find and no context to re-explain over email.
If the reporter ever tells you it couldn’t send something, it means exactly that — nothing was saved, so please email support@tenacap.com and it reaches the same people. We would rather say “that didn’t go through” than take your words and quietly lose them.
What we do with it
Every report is read by the people writing the code, not a support queue that triages it later. We read every one and fix what we can within a day; what we ship shows up in What’s new so you can see the turnaround for yourself rather than take our word for it.