Un solo espacio para entrega, conocimiento e IA

Teams tracked work in one place, wrote knowledge in another, and opened generic chat when they needed help. Context did not carry across, so people repeated themselves and did not trust answers from AI that never saw the workspace. The product needed one governed place where boards, Spaces, and assistant threads all pointed at the same work.

In short: status lives on the board, drafts and reference live in Spaces, and the assistant sits on that same work, not a generic chat window off to the side.

We designed end to end on a shared shadcn Maia system with role-based access. Workspaces and boards carry assignments, due dates, priorities, and lanes so status stays on the board instead of in spreadsheets. Spaces use Notion-style rich text for knowledge and drafts; Create mode and the draft drawer land AI output on real pages. The assistant uses Ask, Plan, and Create, with mentions, workflows, and models curated per workspace, plus reporting with day, week, and month views so leads see movement over time. Home cards and the composer earned the first screen: weekly actions, integrations, and recent work visible at a glance.

Teams stopped treating the board, knowledge base, and chat as three competing truths. Context rode with the work, so fewer reviews opened with a recap nobody had time for, and fewer assistant replies started with "I can't see that workspace." Leads could read movement in reporting instead of stitching a story from side channels and screenshots.