Keep the original context
Keep the original comment, source, and date beside every grouped theme.
CUSTOMER FEEDBACK · PRODUCT DECISIONS
Make customer feedback
useful to your next decision.
Bring requests into one clear workflow, keep each customer’s words attached, and show what the team chose to do. Designed for product teams in software companies of roughly 10–300 people; begin with one team, then expand when the workflow proves useful.
HUMAN CONTROL, BUILT INThe agent can prepare a decision. It cannot approve itself or send an email without your approval.
Free sandbox: fictional data, no account. Early access: request a future real account and source setup.
✓ Customer board and widget✓ Evidence-linked review✓ Human-owned decisions
AAlderlineProduct feedback workspace
FICTIONAL SAMPLEALDERLINE · CUSTOMER PORTAL
24 ideasWhat would make your work easier?
↑42
Connect Linear projects
Needs review“We copy this into Linear every Friday. A link on the feedback card would save the extra step.”
12 comments · Updated today↑26
Weekly team digest
Under review“A short Friday summary would save our Monday morning scroll.”
2 comments · Updated yesterdayBoard · votes · discussion · statusView sample →
TEAM REVIEW · SOURCE KEPT
Needs reviewOne request, with its context.
“CSV export takes me longer than the month-end close. I keep rebuilding the same columns.”
✓Suggested theme2 related requests · 1 source needs confirmationReview first
Source · theme · confidencePeople decide →
TEAM ROADMAP · CUSTOMER LOOP
This quarterDecisions customers can follow.
Export presetsShipped · 18 people following
ShippedScheduled reportsPlanned · linked to 11 requests
PlannedRequest historyUnder review · owner: Maya
ReviewDecision · owner · customer updateClose the loop →
One workflow from customer voice to team decision.Try it yourself →
A clear feedback loop, starting with one product team.
Teams in a 10-person company and product groups inside a 300-person company can begin the same way: keep the original evidence, make decisions visible, and close the loop with customers. Larger rollouts can follow after a team pilot.
See the pattern before deciding
Review votes and repeated asks together before choosing what to build.
Close the loop with customers
Prepare a roadmap update connected to the people who asked.
A feedback workflow with the pieces connected.
Every part serves the same job: collect a request, help the team decide, then close the loop. A team can adopt it on its own, even when the rest of the company is not changing tools.
Public feedback board
Let customers browse ideas, vote, comment, and follow status in a no-signup preview.
In-product widget
Capture a request where the customer is working instead of asking them to find another portal.
Team review inbox
Group similar asks, preserve each source record, set an owner, and record why the team chose a status.
Roadmap and updates
Draft an update for people who voted or commented. A person reviews it before publication.
Connections are planned, not live. The board and widget are the easiest paths to try. Forwarded email and a webhook through tools your team already uses are under consideration; CSV stays a fallback. See the connector plan →
One feedback loop. Two clear views.
Customers share and vote in the portal. Your team reviews those same requests, keeps the evidence, and decides what happens next.
SAME WORKSPACECustomer portal Share · vote · follow status→Team workspace Review · decide · close the loop
A Alderline Studio FICTIONAL SAMPLE
Alderline Community
Realistic sample history · click a post to read the conversation.
Welcome to the Alderline feedback portalVote on ideas, add context, and see what the team is working on.
Recent community activityOct 30 · Aria voted for Linear sync · Oct 29 · Jamal commented on weekly digest · Oct 28 · Priya added a bug report
Top contributors🥇 Jamie 64 · 🥈 Aria 51 · 🥉 Mika 38
Have a different idea? Your team can see it here.
Votes, comments, and dates are synthetic but internally consistent. Changes stay in this browser.
Feedback, right where work happens
Click the button on the sample site to open the feedback widget.
The embedded entry point captures feedback without making customers leave your product.
Team inbox
Turn individual requests into a shared, prioritized picture.
Incoming this week18 itemsSlack · 7Outlook · 4Portal · 5CSV · 2
RISING THEME
Requests are clustering around integrations
Six customers mentioned wanting fewer manual handoffs. Two asked specifically for Linear. Grouping these together helps the product team prioritize the underlying need instead of chasing isolated requests.
✦
Suggested next step
Confirm scope with the team, then share a short roadmap update with everyone who voted.
Agent review queue
Agents collect and organize. Your team approves every decision and external action.
✉
Weekly digest draftPrepared from 18 new items · not sent
Three themes are rising this week. Review the draft, edit the tone, then choose whether to post an update or leave it as a draft.
⌁
Sample sourcesPlanned connectors shown with synthetic records
All sources shown here are synthetic. No OAuth or data sync runs in this prototype.
The product preview uses fictional data and keeps sample edits in this browser. Early-access and founder-conversation requests are sent to VTB Operation; they do not create an account or reserve a meeting.
Three decisions. One clear customer loop.
Keep the work light enough for a founder or product lead to run during a normal week.
Collect the request
Use a feedback board or widget; import a file when your team already has records.
Choose what matters
Review votes and source evidence, group related asks, and record a decision with an owner.
Tell people what changed
Prepare a status or release update linked back to the requests that shaped it.
Intake and connector roadmap · not available yet
Start with the lightest intake path.
No VTB connector or live data import is available today. The preview shows the customer board, product widget, and a local-only CSV migration preview.
Customer board and widget
These are the most direct ways to capture new feedback in the sample workflow. The current preview uses fictional data and does not create a real workspace.
INTERACTIVE SAMPLEForwarded email
A dedicated feedback inbox could let a team forward the conversations it chooses to collect. This intake path is planned; no mailbox is connected.
PLANNEDWebhook through your automation tool
A generic webhook could work with Zapier, Make, or n8n so teams can route selected events without VTB building every connector itself. This is under evaluation, not live.
UNDER EVALUATIONCSV as a fallback
Preview a file mapping locally before anything is imported. The current CSV path stays in your browser and does not upload or apply the data.
LOCAL PREVIEWManaged app connections
A managed connector layer may reduce the work of supporting provider authorization and API differences. No provider has been selected, and no connection is available today.
TO EVALUATEOne-team pilot for larger companies
Early onboarding can be founder-guided. Multi-team permissions and enterprise SSO are future work; an identity provider should support a simple first login and a later SSO path.
BY REQUEST · ROADMAPThese are product directions, not available features. We will test the first routes with a bounded team pilot before expanding across an organization.
Agentic AI with a human checkpoint
Evidence first; policy decides what may proceed; approval is bound to the exact reviewed change.
A DIFFERENT AI JOB
Automation can be useful. Control should be visible.
Different products optimize for different jobs. VTB is designed for teams that want AI to prepare a decision without quietly making it for them.
| Product approach | What the AI is presented to do | VTB Operation’s boundary |
|---|---|---|
| Featurebase · Fibi ↗ | Answer and resolve support questions using enabled knowledge sources. | Suggest with evidence. Keep every source visible, require a human review, and block external actions by default in this preview. |
| Canny · Autopilot ↗ | Find and capture feedback from customer conversations. | |
| VTB Operation · Agent review | Group similar feedback into a proposal for a person to inspect and decide. |
This compares the products’ published AI focus; it does not imply that other platforms lack review controls. Featurebase docs · Canny docs
Propose
Agent drafts a theme or update from cited records, shows uncertainty, and does not silently confirm membership.
Review by risk
Human can approve, edit, reject, defer, or time out. High-impact, external, ambiguous, or irreversible actions fail closed.
Verify and record
Separate append-only decision and execution receipts capture the reviewed payload, policy result, outcome, and verification.
Agent action gate
Inspect the consequence before any agent can change company data or contact another person.
1 · EvidenceSource links, timestamps, match confidence, and uncertainty must be visible.
2 · PolicyCheck workspace, actor, destination, action type, risk tier, and exact payload.
3 · Approval + receiptApproval applies only to the reviewed payload hash; record result and verify it.
Demo buttons only update the local sample. No real task, message, payment, deletion, or provider call is executed. No agent can approve its own proposal or change its own policy.
Availability and price direction
Start free. Pilot one team.
The customer portal and team workspace are two views of the same sample workflow. Start with the product group that feels the pain; broader rollout and enterprise pricing remain a conversation, not a self-serve promise.
Public sample
$0
Explore the portal, widget, review inbox, and approval screens using fictional data. No account, billing, or third-party connection.
Open the preview →One-team workspace
$19 / workspace / month
The current hypothesis covers one workspace and up to 10 teammates. It is not an enterprise quote or a live offer; the scope and price still need validation.
Multiple teams
Scope first
A 100- or 300-person company can begin with one product team. Multi-team access, SSO, rollout support, and pricing need to be scoped with the company.
The $19 amount is a planning hypothesis, not a public offer or an active subscription. There is no live billing or hosted customer workspace today.
Start with one product team.
Explore the free fictional sandbox now, or request a real workspace when onboarding and source setup are available. CSV remains an optional fallback; the preview does not import data.