why a blob, and who's behind it.
plumo started as a thought experiment between two friends who'd both quit a productivity app the same week. the apps were loud, the days felt loud, and we wondered if a tool could just… not be like that.
the first thing we drew was the blob. before the database schema, before the sprint logic, before the MCP integration — there was a small round shape with two eyes, and we wanted to make a tool worthy of it.
we'd both spent years inside the big PM tools — jira, asana, monday, clickup. they're capable systems. they're also unrelenting. they treat you like a resource. they invent urgency. they reward you for showing up every day, and they punish you with red badges when you don't.
we asked: what if the same primitives — sprints, issues, time, dashboards — were just dressed in care? what would change? could a tool be soft on the outside and rigorous on the inside? could a productivity app actually leave you with more energy than it took?
plumo is the answer we kept arriving at. it's a real PM system — used today by teams at dar blockchain, enda dfla, and a handful of others — but every decision is filtered through the question: does this make someone's day softer?
we're a small team in tunisia and france. we're not racing to be the biggest. we're hoping to be the kindest. so far, that's working.
five small principles that shape every decision.
soft is a feature.
gentleness isn't decoration. it's a constraint we apply to every notification, every empty state, every copy line. if it sounds corporate, we rewrite it. if it shouts, we kill it.
rest is a plan.
rest isn't the absence of work — it's part of the work. plumo's rest mode, quiet hours, and "carry forward" affordances all exist because burning out is the most expensive way to ship.
your data is yours.
no third-party trackers, no behavioral profiles, no AI training on your work. export anything, anytime, in one click. if you leave, plumo doesn't hold your team's history hostage.
awareness, not surveillance.
dashboards are for the team, including the people the numbers are about. no hidden manager view. no productivity scores. nothing in plumo is designed to be used against the person it's measuring.
ship slowly, on purpose.
we'd rather be the right tool than the fast one. small monthly releases. honest changelogs. no "redesigns" that break your muscle memory. boring is a feature.
the blob comes first.
if a feature doesn't fit in the blob's voice, we don't ship it. it's the simplest design check we've ever had — and it's worked for a year and a half.
a small team, in tunis and paris.
five people, two cities, one blob. these placeholder bios will be replaced with the real ones soon — but the people are real.
started plumo after years inside loud PM tools. writes most of the backend and quite a lot of the brand. tunis-based. drinks coffee at improbable hours.
responsible for how every pixel of plumo feels. the eight moods, the rounded corners, the slow easing curves — all her. previously at a quiet design studio in tunis.
built plumo's MCP server in a weekend and refused to stop polishing it. believes APIs should be readable as english. based in paris, occasionally in tunis.
writes every word users see. has rewritten "save" as "tuck away" and made it stick. former essayist. doesn't believe in the word "actionable."
made in tunisia & france.
this matters to us. plumo is built in a francophone, EU-adjacent orbit — which means EU data residency by default, real GDPR fluency, and proximity to a growing african + MENA tech scene that big PM tools tend to overlook.