Common questions
Contents
- Why this playbook?
- How frequently is this playbook updated?
- Who keeps this playbook up to date?
- Who owns the legal rights to the software that you write?
- Do you work on-site with partners?
- What tools do we often use?
- What did we use to create this playbook?
Why this playbook?
It reflects how we work, think and collaborate with partners and colleagues, and it exists so that nobody has to guess.
Internally, it keeps teams and projects aligned on the same expectations. Externally, it lets a partner or a candidate know what they are getting into before they commit, including the parts that are inconvenient for us.
It is not exhaustive, and it is not a sales document. It is an attempt to show that business can be done in a clear, structured way, and to be judged on it.
How frequently is this playbook updated?
It is a living document. Sections are updated when a decision changes the practice they describe, and every section is reviewed at least once a year. The date at the bottom of each page tells you when that page was last reviewed. If it looks old, it is old, and you are entitled to ask us why.
Who keeps this playbook up to date?
Anyone in the team can propose a change, and is encouraged to. A section changes when a decision changes the practice behind it. The final call sits with the company’s leadership.
Who owns the legal rights to the software that you write?
You do. The code we develop for a partner is 100% theirs, to use and modify as they see fit. Legal transfer completes on final payment, but the ownership itself is never in question.
Third-party components under open or closed licences stay under their own terms, because we cannot transfer what was never ours. We name them before you commit. Full details in ownership and handover.
Do you work on-site with partners?
We are remote by choice: cost, access to talent, work-life balance and reach. That is our default. But a relationship is not built entirely through a screen, so we meet in person when a project needs it, typically at the start and around key milestones.
What tools do we often use?
Here is a non-exhaustive messy list: discord, slack, google workspace, github, gitlab, vscode, xcode, postman, figma, jira, confluence, prismic, plausible, hubspot, sentry, plus AI coding assistants and agent frameworks (mastra among them) ..
The stack for a partner project is a separate decision: it follows the problem, not our habits.
What did we use to create this playbook?
This playbook is hosted on github and we have used Jekyll with Just the docs, a modern, highly customizable, responsive theme (with built-in search).