Skip to content
Freedomica logo

Process

How we work

No hand-waving. This is what actually happens when you hire the collective.

Planning session at a whiteboard

Behind the scenes

Remote by choice, not by accident

Remote pairing, code reviews and live demos across Tokyo, Hong Kong and our clients’ timezones. No project depends on someone being in a room.

Demo · 2 wk
Code review
GMT-3 → GMT+9
Team collaborating around a table
Notes and a laptop on a quiet desk
Freedomica · Behind the scenes

Step by step

Six steps, zero surprises

  1. 1

    Discovery call

    A 30-minute call to understand the project. You talk to the people who will write the code, not a salesperson.

    • Scheduled within 2 business days
    • Bring sketches, docs or just ideas
    • We tell you honestly if we are the right team
  2. 2

    Scope & proposal

    A detailed proposal with milestones, timeline and fixed pricing per phase. No vague estimates.

    • Delivered within 5 business days
    • 2 to 4-week milestones
    • Risks and assumptions stated upfront
  3. 3

    Squad assembly

    We pick 2 to 5 collective leads based on the stack and domain. You approve the line-up and meet everyone.

    • Clear roles for each person
    • One main point of contact
    • Direct access to the whole team
  4. 4

    Build & iterate

    Two-week sprints with a demo at the end of each. Working software early, not a big reveal after months of silence.

    • Weekly async updates
    • Live demo every 2 weeks
    • Access to the repo and CI/CD
  5. 5

    QA & launch

    Review by at least two engineers, automated tests and a staging environment for your team to validate.

    • Unit, integration and E2E tests
    • Staging for final sign-off
    • We handle the production deploy
  6. 6

    Handoff & support

    Source code, documentation, deployment guides and credentials. The code is yours. Maintenance retainers are optional.

    • Documented codebase
    • Knowledge-transfer session
    • 30 days of bug fixes included

Tools

Our default day-to-day stack

We adapt to whatever your team already uses. But starting from scratch, this is how we set up shop.

Communication

  • SlackSlack
  • Loom
  • NotionNotion
  • Google MeetGoogle Meet

Code

  • GitHubGitHub
  • VS Code
  • Cursor
  • Conventional Commits

Delivery

  • GitHub ActionsGitHub Actions
  • VercelVercel
  • DockerDocker
  • AWSAWS

Quality

  • JestJest
  • Playwright
  • SentrySentry
  • LighthouseLighthouse

Principles

Rules we do not break

Honest scoping

We would rather lose a project than promise an impossible deadline.

The code is yours

Repository, documentation and infrastructure belong to you from day one.

Async by default

Timezones are an advantage when communication is written and clear.

Measurable quality

Tests, monitoring and performance metrics on every project.

Want to see how the work happens?

No mystery: a transparent six-step process with demos every two weeks.