How we work

Managed like an engineering project. Because it is one.

The same sequence for a one-week package or a year-long partnership: understand first, agree in writing, build in short cycles, then keep it running.

Book a call →See pricing
How an engagement runs

You follow every step
in our own software.

Each client gets a project in Firespace App: milestones, documents and approvals in one place, from discovery to support.

FirespaceAPP
Project · ACM
Build Weeks 4–11

Two-week cycles with a demo at the end of each one. Every change is reviewed, tested and deployed by script. You approve each milestone.

ACM-9 Cycle 1 · Accounts and roles Approved
ACM-10 Cycle 2 · Orders and stock Approved
ACM-11 Cycle 3 · Invoices and payments In review
ACM-12 Cycle 4 · Reports and exports Building
Methods ScrumCode reviewCI/CD
Sample project · illustrative
The rules

Six habits behind every project

Named, written down and checked. Nothing here depends on who is on the project that week.

01 Scope before code A discovery maps the problem, the people and the systems. You get a written proposal with scope, milestones, dates and price before anything is built.
02 Milestones you approve Work is split into milestones with an owner, a date and acceptance criteria. Each one closes with your sign-off, in Firespace App.
03 Two-week cycles Every cycle ends with something your team can use and review, and a short written status with risks and the decisions we need from you.
04 Every change reviewed Code goes through review and automated tests before it reaches the main branch. Commits follow one convention, so the history reads like a log.
05 Released by script Releases go out by script, migrations are simulated first, and the deployed version is checked against what was approved.
06 Backups we restore Encrypted backups, kept off-site, and restored on a schedule to prove they work. Incidents get a written follow-up.
Methods

Standards we apply, by area

Delivery PMBOKScrum and KanbanRAID logDecision records
Analysis Stakeholder interviewsBPMN process mapsMoSCoW prioritisationAcceptance criteria
Engineering Code reviewAutomated testsCI/CDConventional commits
Operations Restore-tested backupsUptime and deploy monitoringSecrets in a vaultLeast-privilege access
Where it happens

In our own software, shared with you

FirespaceApp Milestones, documents, approvals and time for every project. app.firespace.co ↗FirespaceDesk Shared inbox and pipeline for WhatsApp, Instagram and Messenger. desk.firespace.co ↗FirespaceSign Proposals and contracts signed online, with the audit trail. sign.firespace.co ↗FirespaceCalendar Discovery calls, advisory sessions and project meetings. calendar.firespace.co ↗

Questions

How long does a discovery take?

Usually one to two weeks, depending on how many areas and systems are involved. It ends with findings, prioritised requirements and a fixed proposal.

Can we start without a discovery?

Yes, for defined work: packages and sprints have a fixed scope and price and can be bought online. Custom projects always start with a discovery.

Who is our contact?

One person leads your project from start to end, and the same team stays with you. You see every milestone in Firespace App.

What happens after launch?

We keep the system live, measured and improving on a monthly plan, or hand it over with full documentation. Your data can always be exported.

Tell us what you are building.

A 30-minute call with the team. We reply within one working day.

Book a call → See pricing