Home / How It Works

How it works

Say what you want done.
Get the finished work back.

There is no dashboard to learn and no prompt to write. You describe the outcome in your own words. Binary works out what the job actually involves, brings in the specialists it needs, checks what they produce, and comes back to you with something finished.

Four steps. The same loop every time.

Walk through the loop See a worked example
  • Plain language in
  • Specialists assigned for you
  • Checked before it reaches you
  • You approve anything that leaves your side
You describe the outcome Binary routes the work Specialists produce Output is checked You receive and decide

The loop

One request in. Finished work out.

Every request moves through the same four steps. Knowing what happens in each one is the whole of learning the system.

  1. 01

    You tell Binary the outcome

    Your part

    Write it the way you would tell a colleague. Binary is reading for the result you want, not for keywords. If something it needs is missing, it asks one question back rather than guessing.

    What helps

    • The outcome, not the task list
    • Who it is for, if that matters
    • Any deadline you are working to
    • Files or links you already have

    What you can skip

    • Choosing which agent to use
    • Prompt wording and formatting
    • Breaking the job into steps
    • Repeating context you gave before

    Example We need a landing page for the new service by Friday.

  2. 02

    Binary routes it to the right specialists

    Coordination

    Binary reads the request, separates it into tracks, and hands each track to the specialist whose job it is. Tracks that do not depend on each other run at the same time. Tracks that do are sequenced, so nobody starts on guesswork.

    What Binary decides

    • Which jobs are actually in the request
    • Which specialist owns each one
    • What runs in parallel and what waits
    • What each specialist must hand back

    Who can be called

    • Pixel for design and visual work
    • Scout for research and sources
    • Lead Hunter for pipeline work
    • Build, content, automation and support

    Handoff Each track carries its own brief, inputs and expected output.

  3. 03

    The work is checked

    Quality gate

    Nothing comes back to you straight from a specialist. Binary reads the output against the brief that produced it. If it misses, it goes back with a note about what is missing. If a specialist could not confirm something, that is reported rather than filled in.

    What is checked

    • Output matches the brief it was given
    • Files are complete and open correctly
    • Claims carry the source they came from
    • Gaps are marked as gaps

    What happens on a miss

    • The track goes back to the specialist
    • The note says what was wrong
    • You are told if it delays the result
    • Nothing half finished is passed off as done

    Rule Unverified work is reported as unverified, not smoothed over.

  4. 04

    The result is delivered to you

    Your decision

    Finished work arrives in the same conversation you started, with a short summary of what was done. Files are saved so you can come back to them. Anything addressed to someone outside your side stops here and waits for your yes.

    What arrives

    • The finished files or previews
    • A short plain language summary
    • Anything that needs a decision from you
    • Open questions, if there are any

    What you do next

    • Approve it, or say what to change
    • Send a revision in the same thread
    • Ask for the source files if you want them
    • Start the next request from here

    Loop A revision is just the same four steps again, with the context already there.

A worked example

Follow one request through the loop.

Pick a request below to see how the same four steps play out. These are illustrations of the routing, not case studies.

You say

  1. 01

    Describe

  2. 02

    Route

  3. 03

    Check

  4. 04

    Deliver

Where you stay in control

Autonomous inside the work. Never past your decision.

The loop runs on its own between these points. At each one it stops and waits for you.

Before anything is sent outside

Emails, messages and posts addressed to someone other than you are drafted and held. They go nowhere until you say yes.

Before a direction is locked in

Design directions and positioning come to you as a preview first, so a long build never runs on an assumption you did not make.

When something cannot be confirmed

A gap is reported as a gap. You decide whether to fill it, drop it, or have someone go and find it.

When the work is finished

Deliverables are saved and checked complete. Approve, revise, or take it and go, in the same thread.

What the loop looks like in practice

One conversation, running in the background.

Requests are not all the same size. The steps do not change, but what you see between them does.

A quick answer

A single question or a small piece of writing. One specialist, one check, back in the thread without a status update in between.

You see The answer, and where it came from.

A piece of work

A page design, a research brief, a prospect list. Several tracks, a check on each, and short progress notes while it runs.

You see Progress notes, then the finished files.

Something recurring

A check that should happen on a schedule rather than when you remember it. Set up once, then it runs and reports on its own.

You see What ran, what it found, and what needs you.

Common questions

Do I have to know which specialist to ask for?

No. Naming one is fine if you already know what you want, but it is not expected. Describing the outcome is enough for Binary to route it.

What if my request contains more than one job?

That is the normal case. Binary separates the jobs into tracks and runs the independent ones at the same time, so you do not have to split the request yourself.

Can I change direction halfway through?

Yes. Say so in the same thread. Binary stops the affected tracks, updates the briefs, and tells you what that changes about the rest.

What happens to the files afterwards?

Finished deliverables are saved and verified complete, so you can ask for them again later instead of having the work redone.

Will anything be sent on my behalf without asking?

No. Work inside your own side runs on its own. Anything addressed to someone outside it is drafted and held for your approval.

CODE BINARY infinite B mark

Start with one request.

Describe the outcome you want in your own words. Binary takes it from there and comes back with something finished.

Start with Binary Meet the digital team

Save time. Let AI carry the work.