How we work
Project, then retainer.
An engagement has a shape. firwat designs the estate, leaves a record, rehearses one restore, and then stays as design authority. The retainer is that authority on the pattern. A per-seat helpdesk is a different business.
Discover
The estate as it runs today: what is true, what is assumed, and what would hurt in a failure.
Design
High-level and low-level design. Named decisions, sequenced so they can be built.
Record
As-built, source of truth, and one restore that has been rehearsed rather than described.
Remain
A retainer of named days. Agreed change stays on the pattern. A new site, tenant, or landing zone is a new project.
Who pays, who owns.
| Item | Who pays | Who owns it |
|---|---|---|
| Switches, wireless, firewalls, servers | The client | The client, including warranty and insurance |
| Microsoft 365, Google Workspace, identity tenant | The client, on their vendor agreement | The client |
| AWS, Azure, or GCP subscriptions | The client | The client. The running accounts are theirs. |
| Designs, as-builts, and automation for that estate | Included in the project | The client may use the artefacts for their estate. firwat keeps the reusable method. |
firwat may coordinate a purchase. Title stays with the client. If a later product hosts a platform for many clients, that platform would be named as such. The first engagement is the client’s own estate.