Project management web app that brings tools and services together via embeds and custom modules. Built with Vue.js, Laravel and Tailwind CSS, with multi-tenant architecture, real-time collaboration and a powerful note editor.
10+
Third-party integrations woven into the platform
It all started with Matt, the CEO of Project.co, when he reached out via our website in 2021. He wanted a team that could take Project.co to the next level — rewriting V1 of the product into something more scalable, modular, faster and future-proof.
The first version had been on the market for a couple of years, serving its original purpose as the project-management tool for Wyzowl, a video production agency handling dozens of monthly projects and clients. But with time, V1 became increasingly hard to manage and extend — it simply wasn't built with modularity in mind from day one.
Project.co V2 had to land a long list of foundational pieces in one swing: a multi-tenant architecture so each company only saw its own data, a modular system that could be extended without friction, a seamless migration path for V1 users, a powerful note editor capable of embedding custom content and components, a robust roles & permissions layer, and a scalable real-time architecture for chat and notifications.
Project.co V2 came together in three deliberate phases — discovery first, then a tight MVP push, then the long arc of turning a working product into a modular platform. The same core team carried the project end-to-end so context never left the room.
Phase 2
The first usable MVP shipped in three months. Alongside the new product we built the import infrastructure that lets V1 customers move across on demand — over 20 GB of historical data flowing into the new multi-tenant model without manual intervention. Multi-tenancy was baked into the data layer from the first migration so we never had to retrofit it later.
Backend & Frontend · MVP Delivery
Phase 1
We started with roughly 90 pages of product documentation. After a series of planning sessions with Matt we digested it down to an MVP scope that was opinionated about what shipped first and what could wait. The stack settled fast — Vue.js, Tailwind CSS, Laravel, MySQL and TipTap for the notes editor — because we'd shipped SaaS on it before and knew the trade-offs.
Solution Architecture · Multi-tenant
Phase 3
With the MVP live, we layered in the pieces that make Project.co feel like a single workspace: a TipTap-powered note editor that embeds custom blocks, an embeds module for external services, fine-grained roles & permissions, and a real-time backbone for chat and notifications. Every module ships as a tool that tenants can enable, configure or hide via permissions and settings — so the product stays simple regardless of how much surface area we add.
Platform Engineering · Modular Architecture
We've owned Project.co V2 end-to-end since 2021 — architecture, backend, frontend, integrations and ongoing product evolution. The same four-person team that shipped the MVP is still the team shipping features today, which keeps the codebase coherent and decisions cheap to make.
After the initial three-month MVP, development never really stopped. We've continued to iterate on UX, data flows and module depth based on what customers actually do once they're live — and we feed product suggestions back into the roadmap whenever something feels off, instead of just implementing tickets.
A familiar Vue + Laravel + Tailwind setup we move fast on, picked for long-term maintainability over novelty. Multi-tenancy lives in the data layer so every feature inherits the right isolation by default.
Vue.js 
Laravel 
Tailwind CSS Every feature ships as a tool tenants can enable, configure or hide — so the product stays simple even as the surface area grows.
Wired in 10+ external services including Zapier, so customers can pull data and automate flows without leaving Project.co.
A scalable real-time layer powering chat, presence and notifications across projects, tasks and notes.
Project.co V2 launched with an intuitive interface that lets each company shape the product to its own workflow — only the tools and data they use are visible. We're still actively building on it today, addressing customer feedback as it lands and adding integrations and modules as the product matures. The platform is integrated with Zapier and a series of third-party tools that let users bring outside data in and automate flows, and it works as well on mobile and desktop as it does in the browser.
“You have done an excellent job of creating Project.co and I am looking forward to working together for the long term. I value the input of your team a lot. Not only do you do very good work but you also make very good suggestions. That's valuable from my point of view as my way of thinking isn't always the best solution so I enjoy hearing what you and your team thinks as well.”
Matt Byrom — CEO, Project.co