CrossX

How it works

A clear rhythm, from first call to every release.

Whether you add one engineer or hand us a whole project, you get the same habits: clear communication, visible progress and decisions made in the open.

Talk to us Compare engagement models
  • Visible progress every week
  • Decisions in writing
  • Your tools, your cadence

Our commitments

Four habits behind every engagement.

  1. We start with your outcome

    Every engagement begins with what you need to achieve and the constraints you work within.

  2. We ship early and often

    Thin, real slices reach production first, so risk surfaces early and progress stays visible.

  3. We decide in the open

    Architecture choices and trade-offs are written down where your team can read and challenge them.

  4. We design for handover

    Documentation, tests and runbooks are part of the work, so your team can run everything we build.

Delivery rhythm

What you can expect, day to day and quarter to quarter.

Staff augmentation follows your team's cadence; project teams follow this one. Either way, these touchpoints keep everyone aligned.

  1. Daily

    Standups and async updates

    Engineers join your standups or post a short written update in your channels, so progress is always visible.

    • Standup
    • Async notes

  2. Weekly

    A written progress note

    What shipped, what's next and any risks, in a note you can forward straight to your stakeholders.

    • Progress note
    • Risk log

  3. Sprint

    Plan, demo, review

    Planning, a demo of working software and a retrospective that turns lessons into improvements.

    • Sprint plan
    • Demo
    • Retro actions

  4. Monthly

    Engagement check-in

    Your CrossX lead reviews progress, team fit and upcoming needs with you.

    • Check-in
    • Team plan

  5. Quarterly

    Look ahead

    A conversation about the roadmap ahead: team shape, skills and priorities for the next quarter.

    • Roadmap review
    • Skills plan

Engagement models

Pick the model that matches who directs the work.

Team extension, a dedicated squad or full project delivery. Toggle between them to compare, and switch whenever your needs change.

Team extension

Individual engineers join your team and work inside your process.

Day-to-day direction: Mostly you

Who directs day to day
Your leads. Our engineers join your standups, boards and code review.
Scope ownership
You own the roadmap and priorities. We own the quality of our engineers' work.
Best when
You have a working team and process and want more experienced hands, fast.
Getting started
The quickest start, because engineers slot into your existing setup.
How you scale
Add or release individual engineers as your roadmap changes.

Dedicated squad

A stable, cross-functional CrossX squad focused on your product.

Day-to-day direction: Shared

Who directs day to day
A CrossX lead runs the squad day to day, working closely with your product owner.
Scope ownership
You set direction and priorities. We plan and deliver the work to get there.
Best when
You want a whole capability, such as a platform or AI team, ready to go.
Getting started
A short setup period to form the squad and agree ways of working.
How you scale
Grow or reshape the squad as a unit, keeping its context and momentum.

Project delivery

A CrossX team owns a defined outcome from discovery to launch.

Day-to-day direction: Mostly CrossX

Who directs day to day
We do. You see regular demos and make the key decisions.
Scope ownership
Agreed up front in a discovery phase, then managed through change as we learn.
Best when
The goal is clear, such as a new product or a migration, and you want one accountable team.
Getting started
Starts with discovery, so the build begins with a shared plan.
How you scale
Add phases or follow-on work once the first release is live.

Tools & practices

Fluent in your toolset from day one.

Our engineers adapt to the tools your team already uses. These are the tools and practices they work with every day.

  • Collaboration

    Live conversations and clear async writing.

    • Slack
    • Microsoft Teams
    • Zoom
    • Google Meet
    • Confluence
    • Notion

  • Delivery

    Work tracked where your team plans it.

    • Jira
    • Linear
    • GitHub
    • GitLab
    • Azure DevOps

  • Engineering practices

    Habits that keep quality high and releases calm.

    • Code review
    • Automated testing
    • CI/CD
    • Infrastructure as code
    • Architecture decision records
    • Runbooks
    • Observability

Next step

Ready to see how we'd work with your team?

Tell us where you are today. We'll suggest the right model and the smallest team that gets you moving.

Talk to us Explore staff augmentation