Run the studio.
Lud Vision is the workspace where money, design, tasks, people, and conversation are one connected graph. A milestone slips two weeks and the runway knows the same day, not at the next board meeting.
One workspace
Tracking, documents and team chat in one place. A chat message becomes work and keeps showing its status.
- Board, List, Roadmap and Insights views
- Custom fields, editable workflows, sub-issues
- Select a doc paragraph to mint an anchored ticket
Integrated runway
Costs aggregate across every ticket, rate and milestone. Change a date, watch the cash position move.
- Live runway, burn and break-even KPIs
- Costs span work items, not a separate spreadsheet
- Scenario switching driven by your timeline
Artist-first pipelines
Concept, model, integration: real art workflows, not an engineering tracker with the words changed.
- Concept, model and integration as first-class stages
- Discipline workloads at a glance
- Milestones and costs that follow the asset, not the ticket
The model is a graph
Revenue edited visually: wishlists, conversion, units, price, net. Every dial shows what it feeds.
- Wishlists to units to gross to profit
- One model behind plan and money, viewed as graph or tables
- Re-forecasts as platform fees and royalties change
One assistant that works everywhere and remembers.
It opens with a keystroke in any Lud product and already knows the studio. Ask a question and it answers from your real data. Ask for the work and it closes the ticket.
- It never has more access than you do. Give a teammate a view-only seat and the assistant is view-only for them too.
- Hand it as much control as you want. Keep confirmation on, or let it act on its own. Every change is recorded and revertible.
“What's blocking the milestone?”
Reads across tasks, docs, chat and the budget, and hands back the blockers as links you click straight through to.
Lud Vision runs Hotshot's planning meetings, sprint tracking and every product document. A balance idea posted in the team channel becomes a costed ticket in the sprint, opens as an experiment in Lud Engine, ships in a build that closes the ticket, and comes back as wishlists that move the forecast through Lud Reach.