Start a project

Software development agency

A software development agency that keeps the record.

Most agencies hand you a status report and, eventually, a zip file. We hand you a workflow run: every requirement, design, implementation, QA result and review as an artifact, with the people who approved each one.

Start a project
governed states per run
9
human gates, every run
2
of transitions in the audit log
100%

What makes this agency different

When to hire an agency, and when not to

An agency is the right call in some situations and the wrong one in others. Here is how we see it.

  1. 01

    You need the whole application, not extra hands

    Ownership from idea to production, including the operations after launch. That is what we do.

  2. 02

    Your team should keep doing its job

    The product people and the operators stay focused, and hold the gates instead of writing tickets.

  3. 03

    You have been burned by a handover

    Code you cannot operate and decisions nobody recorded. The record is the fix.

  4. 04

    You want to see the work as it happens

    Every transition is visible when it happens, not summarised on a Friday.

  5. 05

    You only need staff augmentation

    Then we are the wrong agency. We own outcomes, not seats.

  6. 06

    You want the cheapest hour

    Also the wrong agency. We price per project, against an approved scope.

Do two or more of these apply? Tell us which ones and we reply with how we would run it.

What the agency delivers

How an engagement runs

  1. 01

    Discovery

    A week with the people who own the problem. We write the feature request as the first artifact of the run and agree what done means before anything is designed.

    In the record feature_request, scope, success measures

  2. 02

    PRD and design package

    Research, requirements and design are produced inside the workflow and land in the record as artifacts you can read, comment on and reject.

    In the record research_report, prd, design_package

  3. 03

    Design approval

    A human gate. The run waits until you approve the design package. Nothing is built that the record does not say is being built.

    In the record design_approval transition, logged with the approver

  4. 04

    Development

    Implementation runs as jobs on runners in short cycles. You see every transition as it happens, with the implementation package growing in the record.

    In the record implementation_package

  5. 05

    Automated QA and manual review

    Automated QA runs first and writes a report. Manual review is the second human gate. Failures escalate instead of slipping through.

    In the record qa_report, review_report

  6. 06

    Release and operation

    A release candidate leaves the loop only after both gates pass. We deploy it, monitor it and operate it, and the next request starts the next run.

    In the record release_candidate, released

Sydeso against the usual options

An honest look at how a partner engagement on the platform compares with a typical agency and with building in-house.

Item In-houseTypical agencySydeso
Who owns delivery Your team, alongside everything elseThe agency, until handoverSydeso, through production and after
Where the record lives Tickets, chat and documentsStatus reports and a handover documentArtifacts in a workflow run, with an audit log
How AI is used Whatever each developer usesUndisclosed, or a pitchAgents run bounded jobs inside governed states
Who approves Whoever is availableThe agency PMYou, at two human gates on every run
After launch Your on-call rotaA support contract, if offeredWe operate production and start the next run
Can you take it in-house later It already isDepends on the handoverYes: the platform is public and the record is yours
Price Salaries and toolingDay rates or fixed pricePer project, scoped at discovery

Three ways to work with us.

Questions

How do you price agency work?
Per project, against the scope written in the PRD at the end of discovery. Discovery is a week. Operation after launch is a separate monthly engagement.
Can you work with our in-house team?
Yes, as the people who hold the gates and own the product. Your team approves design packages and reviews release candidates; ours runs the work between those gates.
Where is the work done?
On the Sydeso platform, with jobs on managed runners or runners inside your network. The record is visible to you throughout.
What if we want to take it in-house later?
Self-host the platform, keep every artifact, and run the next feature request yourselves. That path is open from day one.
How quickly do you reply?
By email, with how we would run the work, not a call to book a call. Send one paragraph about what should ship first and you get a written answer.
Do we have to use the Sydeso platform?
Every partner engagement runs on it, because the record it keeps is how we work. You can host it yourself from day one or move to self-hosting later; the platform is public under BUSL-1.1.
What happens to the work if we stop?
Everything is in the record as artifacts: requirements, design packages, implementation packages, QA and review reports. You keep all of it, and the platform that reads it is yours to run.

Related

Tell us the feature.

One paragraph about what should ship first. We reply by email with how we would run it, and what it would cost.

Start a project