Before Closot, their teams were spread across a dozen tools: external documents for specs, a legacy wiki for knowledge bases, a legacy project tracker for tickets, another workspace tool for notes, a separate task manager for marketing tasks, a docs tool for meeting agendas, a video tool for walkthroughs, a spreadsheet app for CRM experiments, a shared calendar app for scheduling, a board tool for the design team's pipeline, a separate ops management tool for the ops team, and team chat for everything in between. Information was everywhere and nowhere. When a new engineer asked "where do I find the API guidelines?", the answer was genuinely uncertain — it could be in any of four tools.
This is the story of how the company consolidated all twelve into a single Closot workspace, team by team, workflow by workflow. We interviewed their Head of Engineering, VP of Product, and several team leads to understand what worked, what was painful, and what the real impact has been six months later.
The migration strategy
Migration happened in three phases over six weeks. First: all documentation. Second: project management. Third: internal wikis and knowledge bases. The key insight was not replicating old workflows exactly, but redesigning how information flowed between teams using Closot's linked databases and cross-team views.
Their Head of Engineering, Derek, put it this way: "We made a mistake early on trying to recreate our legacy tracker boards exactly in Closot. The moment we stopped doing that and asked 'what do we actually need to see?', everything clicked. Closot's board views are flexible enough that we could build something better than what we had."
Engineering: Sprint boards and cycles
Engineering was the first team to migrate, and the hardest. They had 18 months of legacy tracker history, custom fields, and deeply ingrained workflows. The team set up sprint boards with kanban views for daily work and timeline views for quarterly planning. Each two-week cycle pulls tickets from a prioritized backlog, and Closot's velocity tracking shows points completed versus planned across the last eight sprints.
The breakthrough came when they realized they could create linked database relations between their sprint board and the product roadmap. Every engineering ticket now traces back to a product initiative, and every product initiative shows its linked engineering work in a roll-up view. When a PM asks "how much of Project Mercury is done?", the answer is live and always current.
Product: Roadmap in timeline view
Product replaced their previous workspace tool and external document editors with Closot pages for specs and the timeline view for roadmapping. Their quarterly roadmap is a single database displayed as a timeline, with each initiative represented as a bar spanning its planned duration. Dependencies render as connecting lines. Color-coding by team makes resource allocation visible at a glance.
Product managers also adopted Closot AI Agent for processing customer feedback. The agent scans incoming requests, categorizes them by theme, and links them to existing roadmap items. Their VP of Product told us: "We used to have a monthly meeting to review customer requests. Now the agent does the categorization continuously, and we just review the patterns."
Marketing: Content calendar in calendar view
The marketing team replaced their previous task manager with a Closot board that they primarily view as a calendar. Each content piece — blog post, social media campaign, email newsletter, product launch announcement — is a ticket with a publish date, status, assignee, and content type label. The calendar view gives them a visual overview of the month, and they drag items to reschedule.
They also built an editorial workflow using Closot automations: when a draft moves to "Ready for Review", it automatically assigns the editor and sends a chat notification. When it moves to "Approved", it notifies the social media coordinator. The entire pipeline runs without manual handoffs.
HR: Onboarding wiki with verification dates
HR migrated their onboarding documentation from the legacy wiki to a Closot wiki with verification dates. Every onboarding page has an assigned owner and a verification schedule — benefits information is verified quarterly, security policies monthly, office logistics annually. Pages that are overdue for verification display a yellow banner, and owners receive automated reminders.
New hire onboarding is now a Closot Marketplace template: HR clicks "New Onboarding", enters the hire's name and team, and the agent creates a personalized onboarding space with role-specific reading lists, a 30/60/90 day plan, and pre-assigned tasks for the manager. What used to take HR three hours of manual setup now takes five minutes.
Sales: Pipeline in board view
The sales team built their pipeline as a Closot board with a kanban view: columns for Lead, Qualified, Demo Scheduled, Proposal Sent, Negotiation, and Closed. Each deal is a ticket with custom properties for deal size, expected close date, and account tier. A dashboard shows pipeline value by stage, win rate trends, and individual rep performance.
The messaging integration proved critical for sales. Reps create deal updates directly from chat by mentioning @Closot — "update Acme Corp deal to Proposal Sent, $85K" — and the agent updates the ticket without anyone opening the workspace. Weekly pipeline reviews now pull data from the live dashboard instead of manually assembled spreadsheets.
Company-wide: Meeting notes and universal search
Every team now uses Closot meeting notes. Calendar events automatically generate a notes page from a template. After the meeting, the AI generates a summary with action items, which become tickets on the relevant board. Six months of meeting history is fully searchable through universal search — their Head of Engineering told us this alone justified the migration.
What the team would do differently
Derek shared two lessons. First: "Migrate docs before projects. When your documentation is already in Closot, migrating project management feels natural because the specs and wikis are already there to link to." Second: "Don't try to get every team on board simultaneously. Start with the team that's most frustrated with the current setup — they will be your best advocates internally."
The biggest qualitative change was not about cost savings or time savings, though both were significant. It was about coherence. When a new engineer joins the company today, all the context is right there — the spec, the sprint board, the meeting notes, the wiki, the decisions. Everything lives in one place, connected by links and databases that stay in sync automatically.