SFreedom
How we work

Five steps. Each one ends in your hands.

You always know what was done, what is next, and where to try it.

  1. 01Discovery
    What happens
    • A call about the goal, the users and the limits
    • We read what already exists: code, docs, contracts
    • Risks and open questions written down
    You get
    A written specA plan split into stages
    Your part

    Answer questions and agree on what is out of scope. The spec is yours even if you stop here.

  2. 02Design
    What happens
    • Screens and flows on a shared design board
    • Motion and states tried in the browser
    • An architecture sketch for anything with money or data
    You get
    A clickable prototypeAn architecture note
    Your part

    Comment right on the screens. The board changes until you approve it, then the build starts.

  3. 03Build
    What happens
    • Short iterations, each ending on a test address
    • Tests on every change
    • A weekly written update with links
    You get
    A test addressA weekly update
    Your part

    Try each step on the test address and reply in the chat. Changes go into the next iteration.

  4. 04Launch
    What happens
    • Production setup, domains, secrets in a manager
    • Backups and alerts switched on
    • A final check of the money and data paths
    You get
    Production, with your OKAn engineering record
    Your part

    Give the final OK. Nothing goes live without it.

  5. 05Run
    What happens
    • Monitoring and alerts to a shared chat
    • Updates and security patches
    • New features through the same steps
    You get
    Alerts and backupsNew work, same steps
    Your part

    Report issues in the chat and plan new work together.

Communication

One job per channel.

Each channel has one purpose, so nothing gets lost between them.

working daysOne shared chatQuestions, quick decisions and alerts. One chat per project.
every weekA weekly updateWhat shipped, a link to each part, what comes next.
after each stepA test addressEvery finished step, live, before it reaches production.
during designDesign boardScreens and flows; you comment on the exact spot.
when neededCallsFor decisions that need talking. Written notes follow.
Feedback loop
Nothing goes live
without your OK.

You comment on the board or in the chat. The answer comes in the same thread, the change lands on a test address first, and it reaches production only after you approve it.

Standards

Every project gets these.

/stack →
A test copy of every projectEach step is live on a test address before production.
Secrets in a managerKept in a secrets manager and encrypted config.
Nightly backupsStored off the server and kept for seven days.
Alerts to a chatIf something breaks, it shows up in the chat within minutes.
An engineering recordEach system is written up: parts, data, money path.
Start a project