- Bots, dashboards and community integrations
- Websites and APIs
- Internal tools for community and support teams
- Written scope and change control
Best for: teams that need a specific tool built well and maintained.
Services
Purpose-built tools, scoped and delivered against clear milestones.
Best for: teams that need a specific tool built well and maintained.
The software in question, built to your specification.
Any substantial change or addition to the specification requires renegotiating the cost of the work.
These are rough estimates to help you gauge scale, based on typical projects. They are not quotes, and every project is different. We provide a quote during your introductory meeting, once we understand the scope of your work. Estimates do not include taxes or third-party costs such as hosting and licences.
Every client has a dedicated account executive, who is your liaison with the company. They are responsible for delivering the work and for keeping communication clear, and they escalate to Naomi whenever it is needed.
Custom builds are scoped as fixed projects, with changes to scope agreed in writing. Every engagement is scoped in writing, so you know what is included before work begins.
Start by sending a project enquiry. If it looks like a fit, we schedule a short introductory call to evaluate it, and we do not invoice for that call.
How we work
Tell us about your community or project. We typically reply within 3 to 5 business days.
If it looks like a fit, we schedule an introductory call at the next available time. We arrange it ourselves, and we do not charge for it.
We provide a quote during that meeting, once we understand the scope of your work.
No work begins until a written service agreement is signed. We begin at the start of the contract term.
A dedicated account executive, a weekly update and a single place to ask questions. Confidentiality is included at no cost.
We look at the results with you, adjust the plan, and decide together whether to continue, change or stop.
Examples of this kind of work, with the results and the people who wrote about it.
A unified support workflow that brings community questions from Discord, GitHub and Slack into one place, with automation to track and answer them.
Read the study on One help channel across Discord, GitHub and Slack
A ground-up rebuild of a JavaScript SDK from alpha to general availability, and cross-language parity across a family of voice SDKs.
Read the study on Rebuilding a JavaScript SDK and keeping several in step
A moderation bot, an economy and engagement system, and staff tools, built for a community of more than 300,000 members.
Read the study on Moderation and engagement tooling for a 300,000+ member community
Questions
These answers describe how we usually work. The binding terms of any engagement are set out in your written service agreement.
Most clients start with one and grow into another.
The day-to-day running of your community, so your team can stay focused on the product.
Engineering capacity for the projects and tools your developers depend on.
A fixed-scope engagement that gives your community structure, policy and direction.
A one-off refactor of a codebase that was built quickly, so it is easier to maintain, faster and safer to run.
Structured mentorship from experienced engineers and community professionals, for individuals building a career and for companies growing a team.
Tell us about your community or project, and we will tell you honestly whether we can help.