SoftSora
HOW WE WORK

Forward-deployed. Measured. Owned.

Senior engineers work inside your operation, with an AI-native squad behind them.

  1. 壱Outcome Call

    30 minutes · free · no commitment

    You can stop here.

  2. 弐Outcome Sprint

    2 weeks · fixed fee

    You can stop here.

  3. 参Production Pilot

    4 to 6 weeks · fixed price

    You can stop here.

  4. 四Deploy & Run

    Ongoing · monthly fee

01 · FORWARD DEPLOYED ENGINEERING

One team that answers for the result, not the hours.

Colombo working hours overlap Tokyo, Dubai and Berlin every weekday.

  • Colombo
  • Tokyo
  • Dubai
  • Berlin
With you

Forward Deployed Engineer

A senior engineer who learns your workflow and makes the technical calls.

Deployment Lead

Owns the plan, the KPI and the weekly proof.

Behind them

AI-native squad in Colombo

Engineers with coding agents build and test behind them.

02 · THE SORA METHOD

Agents build. Engineers own.

  1. Frame

    Agree one business KPI

    With its baseline, in writing.

  2. Prove

    A working slice

    On your real data, measured.

  3. Deploy

    Production, signed off

    With security review and handover.

  4. Run

    Operate and improve

    Weekly proof against the KPI.

Sora AI Core

Our reusable foundation, Sora AI Core, runs on your cloud and is what lets a Production Pilot take 4 to 6 weeks.

03 · FOUR STEPS

Start small. Stop at any step. Scale what works.

You pay for agreed outcomes, not hours. Every step has a fixed fee, a written definition of done, and a clear point where you can stop.

    • 30 minutes
    • free
    • no commitment

    Outcome Call

    An engineer and a Deployment Lead talk through the outcome you want and whether we are the right team. NDA first if you need it.

    Exit

    A written note of the outcome, the KPI and a proposed Sprint, or a clear "not us".

    • 2 weeks
    • fixed fee

    Outcome Sprint

    KPI definition, baseline from your data, working slice or technical spike, risk and security review, pilot plan with a fixed price. Fee agreed before we start, credited toward the next step if you continue.

    Exit

    Go / no-go report.

    You can stop here.

    • 4 to 6 weeks
    • fixed price

    Production Pilot

    One workflow live in production on your systems, measured against the Sprint baseline, with security review and handover documentation.

    Exit

    Measured result against the baseline.

    You can stop here.

    • Ongoing
    • monthly fee

    Deploy & Run

    Rollout, operations, monitoring and improvement; weekly proof against the KPI; a named owner at every level. Part of the fee is linked to your agreed KPI.

    Exit

    Full handover: code, documentation and runbooks, on agreed notice.

04 · OUTCOME-LINKED FEES

Fixed fees first. Then part of the fee follows your KPI.

We do not publish a price list. You always know the cost of the next step before it starts.

Before we build anything, we agree with you in writing on one business KPI, how it is measured, where the data comes from, and the baseline it is measured against.

If the KPI does not move, you see it in the same data we do.

Contract types for Japan, in Japanese
  • Fixed feeOutcome Sprint · Production Pilot

    The Outcome Sprint and the Production Pilot are fixed-fee, so you know the cost before work starts.

  • Linked to your KPIDeploy & Run

    In Deploy & Run, part of our fee depends on that KPI.

Written into the contract
  • The KPI definition
  • The baseline
  • The measurement method
  • The events excluded from measurement

We review the results with you on an agreed schedule.

05 · GOVERNANCE

A named owner at every level, and proof every week.

  • 01

    Your code in your repositories from day one.

  • 02

    AI-written code goes through your normal review, and a named engineer signs off every release.

  • 03

    Your data stays in your cloud and region, and is never used to train outside models.

  • 04

    A named owner at every level: project lead, CTO, CEO.

  • 05

    Weekly proof: what shipped, what moved, what is at risk.

Visit the Trust Center
06 · FAQ

What procurement asks first.

Request the security pack
What if the KPI is missed for reasons outside your control?
The contract lists these events in advance, together with the things we depend on from your side. Examples are changes in business volume or policy, outages in upstream systems, and data or system access that we need but do not receive. If one of them affects the KPI, we tell you promptly and show the effect with data. The affected period is then excluded from measurement or re-baselined, as the contract sets out. The aim is that neither side carries the cost of events it cannot control. If the KPI is missed for reasons within our control, the KPI-linked terms apply as agreed and we give you a written plan to recover.
Who owns the code?
You own the IP we deliver. We license generic accelerators, such as Sora AI Core components, for reuse where applicable.
WHAT WE BUILD WITH

A stack chosen for longevity, not novelty.

We choose established tools that clients can hire developers for and maintain after handover. Our team focuses on a few ecosystems and knows them well.

Product

  • React
  • Next.js
  • Angular
  • Vue.js
  • TypeScript
  • Tailwind CSS
  • Ant Design
  • React Native
  • Flutter
  • Swift
  • Kotlin
  • Figma

Services & data

  • Node.js
  • Python
  • Java
  • Spring Boot
  • .NET
  • Go
  • GraphQL
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Elasticsearch
  • Bruno

Cloud & delivery

  • AWS
  • Azure
  • Google Cloud
  • Firebase
  • Docker
  • Kubernetes
  • Terraform
  • GitHub Actions

AI

  • PyTorch
  • TensorFlow
  • OpenAI
  • Anthropic
  • Claude

Two weeks to a measured answer.

The 30-minute Outcome Call is free. An engineer replies within one business day.

Start an Outcome SprintRequest a proposal