Values · Transparency
We say what's true, even when it costs us.
Published pricing, a public roadmap, and limitations stated up front. If a competitor fits you better, we'll tell you.
How
Three ways we practice it.
Transparency is easy to claim. This is what it looks like in how we run TestPlanIt.
Honest pricing
No 'contact sales' for the real price and no per-feature upsells. The number on the pricing page is the number you pay.
Public roadmap and changelog
Every shipped feature, bug fix, and trade-off is documented in public. See what we built last week and what's next.
We tell you what we don't do
If TestPlanIt isn't the right tool for your use case, we say so. If a competitor does something better, we admit it.
In practice
What honest positioning looks like.
The test management space is full of vague promises and curated demos. Here is how we try to be different.
What we'll tell you
- Exact pricing, with no 'call for quote' tiers
- What features are still rough or unfinished
- When a competitor fits your needs better
- Bugs we know about and when they'll be fixed
- The real reason behind product decisions
What we won't do
- Dark patterns to force upgrades or renewals
- Vague benchmark claims without methodology
- Hidden fees, usage throttles, or surprise charges
- Comparison pages that cherry-pick weaknesses
- Marketing speak that doesn't match reality
Side by side
TestPlanIt vs. marketing-first vendors.
Most vendors optimize for the sales funnel. We optimize for the relationship after you've signed up.
| Capability | Typical Vendor | TestPlanIt |
|---|---|---|
| Pricing | 'Contact sales' for real numbers | Published rates, no negotiation needed |
| Limitations | Buried in fine print or docs | Stated upfront on feature pages |
| Roadmap | Curated marketing timeline | Public GitHub issues and milestones |
| Changelog | Quarterly 'What's new' posts | Every commit is a publicly readable change |
| Comparisons | Competitor weaknesses only | Honest trade-offs, both directions |
| Bug reports | Private support ticket silo | Public GitHub issues, open discussion |
Your choice
Transparency as a habit.
Not a one-time post. Three practices we commit to.
Public documentation
All docs are open and versioned in git. If something is wrong or unclear, file an issue or fix it yourself.
Real release notes
No batching fixes into vague 'improvements.' Each release notes what changed, what broke, and what we learned.
Public post-mortems
When we ship a regression or an outage, we write about it publicly. Trust is built by how problems are handled.
- Roadmap & issues
- Public
- Commit is a changelog
- Every
- Hidden pricing tiers
- Zero
- Bug & issue tracker
- Open
Who it's for
Built for teams that check the fine print.
- Budget owners
- Published rates with no 'contact sales' tiers, hidden fees, or surprise charges.
- Teams comparing vendors
- Comparisons that state trade-offs in both directions, including when a competitor fits better.
- Engineers evaluating fit
- Limitations and unfinished features stated up front on feature pages, not buried in docs.
- Teams that report bugs
- Public GitHub issues and open discussion instead of a private support ticket silo.
Check our work.
Read our pricing, our GitHub issues, and our commit history. Then decide if we're worth trusting with your team's testing.