Known Limitations
Confab is in a closed-beta MVP state. The goal of this release is to validate the core decision loop, not to present a finished platform with every edge polished.
This page sets expectations so teams can evaluate the right things.
Current Product Focus
The MVP is strongest when you use it for:
- a real decision with a small group
- a short list of options
- structured questions or attributes
- asynchronous collaboration
- compare, feedback, and a recorded outcome
If you use the product that way, you are testing the part that matters most.
Areas That May Still Feel Rough
First-run onboarding
The product direction is clear, but some first-run paths and empty-state cues may still feel less guided than they should.
Surface-area breadth
Some pages or concepts may appear broader than the current MVP focus. Not every visible surface is equally important to the beta.
Analysis depth
Analysis exists, but the MVP should be judged primarily on whether Compare and Feedback help teams understand their decision. Analysis depth is secondary for this phase.
Documentation completeness
The docs are being actively aligned to the current product and release scope. Some reference areas may still be catching up.
What Should Not Block A Beta Evaluation
These are not the main product criteria for the current release:
- advanced analysis customization
- file-heavy workflows
- broad workspace administration polish
- enterprise identity and provisioning features
- billing and pricing controls
- third-party integrations
If one of those becomes a blocker for your real use case, note that clearly. Otherwise, evaluate the product on the core decision loop first.
What Would Count As A Serious Problem
These issues are more important than polish complaints during the beta:
- unclear first action
- invite acceptance failure
- inability to submit responses reliably
- compare or feedback failing to clarify trade-offs
- inability to record or lock the outcome
If you hit one of those, report the exact step, what you expected, and what happened instead.
How To Use This Page
Use this page as a reminder to separate:
- rough edges that are acceptable in an MVP
- blockers that make the decision workflow fail
That distinction helps the team improve the right things first.