5 pages · 18 features
spec/project.md
Customer feedback portal
Product goal
Help product teams turn repeated customer feedback into visible roadmap decisions.
Primary users
Product managers, support leads, and customer-facing founders.
Current Build
Build the feedback inbox, triage review, roadmap preview, and publish-ready settings.
Feedback Inbox
Sources
Accept CSV feedback, support ticket excerpts, sales notes, and manual entries.
Clustering
Group related feedback by product area while preserving original quotes.
Priority score
Compute impact from account tier, frequency, urgency, and confidence.
Triage Review
Decision states
Each theme can be accepted, rejected, deferred, or returned for more evidence.
Owner assignment
Accepted themes must have an owner before roadmap publication.
Audit trail
Every decision stores the reason and visible customer evidence.
Roadmap
Columns
Show Now, Next, Later, and Published groups with customer-facing labels.
Changelog
Each changelog card links back to the feedback themes that informed it.
Preview
Roadmap cards must be reviewable before publish.
Build Plan
Group 1 — Feedback inbox
Build feedback inbox import, clustering, and priority score.
Group 2 — Triage workflow
Build triage decisions, owner assignment, and audit trail.
Group 3 — Roadmap
Build the previewable roadmap and publish-ready settings.
Preview Active
Feedback that ships.
Turn every customer signal into a decision your whole team can see — from inbox to public roadmap.
Get started Watch the film ›
New feedback 128 ↑ 18% this week
Northwind Acme Lumen Vertex Polar
Designed for the whole loop.
Capture, decide, and ship — without losing the thread.
Imports tickets, calls, and notes into one reviewable queue.
Groups duplicate requests while keeping every original quote.
Shows customers exactly what changed after each build.
Decisions
Every call, on the record.
Accept, defer, or decline with a visible reason trail your customers can actually trust.
See how it works › SAML onboardingAccepted Bulk reviewer invitesShipped Audit log exportNow
Simple, transparent pricing.
Start free. Upgrade when your loop grows.
Starter
$0/mo
- Up to 3 reviewers
- 1 public roadmap
- Community support
Pro
$29/mo
- Unlimited reviewers
- Clustering & priority scoring
- Changelog & previews
Scale
Custom
- SSO & audit logs
- Priority SLAs
- Dedicated success
Why Castaly
Shape the spec. Build with confidence.
Turn ideas and references into a clear Product Spec.
Castaly asks questions instead of filling gaps with guesses.
Every build stays aligned with the approved spec.
Build Control
Build with control at every step.
Each change follows a clear path and returns to the spec before the next iteration.
Understand First
Before AI builds, Castaly understands.
Castaly turns rough ideas into clear decisions, structured plans, and a ready-to-build spec.
Choose a billing model before execution begins.
Connected Context
Every decision stays connected to the build
Decisions, impacted surfaces, spec updates, and builds stay within the same project context.
01 Approved decisions
Chat
Decisions captured in conversation
02 Impact map
Structure
Mapped across the product
03 Source of truth
Spec
Written into the source of truth
04 Execution plan
Build
Built from approved context
What users notice first
Clear decisions, consistent context, and a smoother path from idea to working product.
I can see what Castaly will build before the build even starts.
When something is unclear, Castaly asks instead of making assumptions.
The spec gives every build a clear starting foundation.
Preview feels like a review step, not a surprise at the end.
Feedback becomes a scoped change, not another vague prompt.
I know exactly which part of the product a decision impacts.
The build plan gives me clear checkpoints to review and approve.
Each next step starts from approved context, not the previous message.
Small changes stay tied to the spec and the specific screen they affect.
I can clearly tell when we’re still deciding and when we’re ready to build.
Every iteration can be traced back to a specific decision.
The current version is understandable without revisiting the entire chat history.
Stakeholders can review direction before work moves forward.
The loop is simple: decide, spec, build, preview, refine.
It feels like building with control, not prompting into the void.
