About
One system, and a long list of noes
A company of thirty or three hundred does not lack tools, it lacks one place where the role, the process, the work and the number are the same records.
Decisions
Four things we decided early on
- One data model, or it is a suiteA suite is several products with a shared login. What makes this one system is that a task, a role, a process, a measure and a goal are the same objects everywhere, referenced rather than copied. Everything good about the product comes from that, and so does everything hard about building it.
- The scope is people and workThis is a people and project management system. Payroll, benefits, leave, attendance, invoicing, a CRM and a helpdesk are not in it and are not coming. Naming the edge is more useful to you than a longer feature list.
- Say the priceStarter is free for up to 10 people. Growth is per member per month, authored in USD, INR, AED, SGD, GBP, EUR rather than converted from a stale rate. Only the top tier is quoted, and the reason is that it is genuinely negotiated.
- A claim is a flag, not a sentenceEvery claim on this site that depends on a feature reads a flag in the code, so a page cannot say a thing ships because somebody typed it. Where a mechanism is unbuilt the page says what happens today instead, in the same place, in the same size type.
Verify it
Check anything we say on this site
- RoadmapFour columns, and only the first one means you can use it today.
- ChangelogWritten from the repository, not from a release calendar.
- SecurityNames what we hold, which is currently no certification at all.
- CompareSays what a stack of separate tools does better, because some of it is better.
If you find something on this site that is not true, that is a defect, and we would like to hear about it more than we would like to keep the sentence.