Bugs are annoying. You've spent time configuring an agent or running a workflow, and something didn't behave the way it should. That's a genuinely frustrating moment, so we want to turn it into a useful one.
The Bug Bounty Programme rewards you with credits for every genuine bug you report and we validate. The more helpful your report, the faster we can fix it...and the more credits land in your workspace wallet!
This article covers what counts, what doesn't, and how severity tiers map to credit rewards.
How the programme works
You hit something weird in Evergrowth
You submit a bug report from inside the platform
Our Engineering team validates it and assigns a severity tier
Credits are added to your workspace wallet, and we notify the reporter
No forms to chase, no emails to send. Everything happens in-app.
💡 Credits are added to the workspace wallet, not the individual reporter. That way the whole team benefits — and there's no awkward "whose credits are these" conversation.
What counts as a bug ✅
A bug is a defect where Evergrowth doesn't behave the way the documentation, in-app copy, or expected workflow says it should.
Good examples:
An agent output that's empty or malformed when it shouldn't be
A workflow that fails silently halfway through
Filters that don't return the records they should
A CRM sync that drops fields or writes incorrect values
A button that does nothing when clicked
Data that appears in the wrong account or contact
Authentication or permissions behaving incorrectly
If you can describe "I expected X, but Evergrowth did Y" — and X is supported by our docs or obvious from the UI — that's a bug.
What doesn't count ❌
Some things feel like bugs but are actually something else. These don't qualify for bounty credits:
Feature requests — "I wish Evergrowth could do X". These are welcome and genuinely useful, but they go in our feedback channel, not the bounty programme.
UX preferences — "I'd prefer this field to be in a different place". Valuable feedback, but not a defect.
Agent outputs you disagree with — if an agent returns a qualification or signal you don't agree with, that's a tuning conversation, not a bug. Your CSM can help you refine it.
Third-party issues — if Salesforce, HubSpot, or another connected system is down, the symptoms may appear in Evergrowth, but the bug isn't ours to fix.
Documented limitations — anything we've explicitly noted as "not yet supported" in our docs.
Duplicates — if someone has already reported the same bug, only the first reporter earns credits.
NB: If you're unsure whether something qualifies, submit it anyway. We'd rather tell you "that's a feature request" than miss a real bug.
Severity tiers & rewards
Every validated bug is assigned one of four severity tiers. The tier determines the credit reward.
Tier | What it looks like | Reward |
P3 — Cosmetic | Spelling error, minor visual bug, UX quirk that doesn't block work | 25 credits |
P2 — Functional | Annoying defect that slows you down but can be worked around | 50 credits |
P1 — Broken workflow | Blocking defect, incorrect agent output, data integrity issue | 100 credits |
P0 — Security | Auth bypass, data exposure | 150 credits |
💡 Pro Tip: The clearer your report, the faster we can triage.
Include what you were doing, what happened that was unexpectd, and any other details to help us identify what went wrong.
Attaching a short recording like a Loom video is massively appreciated!
How to submit a bug report 📢
Step 1) (Ideally on the page you experienced the bug) Click the trumpet icon (bottom-right of any Evergrowth page)
Step 2) Fill out the details of the bug
Step 3) Click Send Bug Report
Your report lands directly with our Engineering team.
You'll get a confirmation in-app and an email when it's been triaged.
What happens after you submit
Our Engineering team reviews every submission, usually within two working days.
One of three things happens:
Validated as a bug → severity assigned, credits added to your workspace wallet, you get a notification with the tier and reward
Not a bug → we explain why (feature request, working as designed, third-party issue, etc.) and redirect you to the right place
Need more info → we'll reach out for clarification before we can validate
If it's a P0 security issue, we'll prioritise it immediately and may reach out directly to coordinate a fix before any public discussion.
A note on security reports
If you believe you've found a security vulnerability — auth bypass, data exposure, any cross-tenant issue — please submit it through the in-app form, not through public channels.
Responsible disclosure protects our entire customer base. We take every security report seriously, and the P0 tier reward reflects that.
Fine print
A few things worth knowing:
Credits are added to your workspace wallet and behave like any other credits
Each bug is eligible for one reward — the first valid reporter wins
Evergrowth employees and contractors aren't eligible (sorry team 😢)
We reserve the right to adjust severity after deeper investigation, though we'll always explain if we do
The programme may evolve — we'll update this article when it does