Services Solutions Work Process Resources Company FAQ Contact Free AI audit

Home / Process

How we work

A process you can set your watch to.

Five phases. Fixed scopes. No open-ended billing, no mystery milestones. You always know what happens next, what it costs, and when it's done.

The five phases

From first call to running system.

  1. Week 1 · Free

    Free AI audit

    We map your workflows, interview your team, and measure where the hours go. You get a written report: automation targets ranked by ROI, infrastructure risks ranked by severity, and a savings estimate you can check. Free, one week, no obligation — and yours to keep even if we never work together.

  2. Week 2 · Locked price

    Roadmap & fixed-scope pilot

    We turn the audit into a plan: what we build first, what it costs, and what "done" looks like — in writing. The pilot is one pipeline or one system, scoped tightly enough that we can price it fixed. You approve the scope; the price doesn't move unless you change it.

  3. Weeks 3–8 · Demo every Friday

    Build & integrate

    Senior engineers build in your infrastructure (or ours, your choice) with a staging environment from day one. Weekly demos, real data, honest status. You see progress every week — never a big reveal at the end.

  4. Launch + 30 days

    Handover & train

    Documentation, runbooks, recorded training sessions, and shadow operations where your team runs the system with us on call. When handover is done, your team can operate everything without us. That's the bar.

  5. Ongoing · Cancel anytime

    Managed run (optional)

    Many clients keep us on a managed plan: we operate, monitor, and keep improving the system while your team focuses on the business. Month-to-month after an initial term. Cancel anytime — everything is already yours.

Week by week

A typical four-week pilot.

This is the actual cadence of a fixed-scope AI automation pilot. DevOps and web builds follow the same rhythm with different week-2/3 tasks.

pilot schedule · AI automation
$ seiko pilot --scope ai-automation
week 1 — audit: workflow interviews · baseline metrics · targets ranked
→ output: written audit report + fixed-price pilot proposal
week 2 — design: pipeline architecture · agent specs · review gates defined
→ output: design doc approved by you before any code
week 3 — build: agents + QA gates + approval queue · staging from day one
→ output: working pipeline on real data · weekly demo
week 4 — harden: edge cases · load testing · runbooks · training sessions
→ output: production deploy + handover package + 30-day fixes
launch in 4 weeks. fixed price.

Engagement models

Three ways to work with us.

Fixed-scope pilot

One system, one price, 3–6 weeks. The way every relationship starts. You get a working result and a team you can evaluate before committing further.

Project build

A larger defined build — platform, portal, full pipeline suite. Fixed price, milestone payments, weekly demos. Typical range: 6–12 weeks.

Managed run

We operate and improve what we built: monitoring, incident response, continuous improvement. Monthly, cancel anytime, everything documented and yours.

Guarantees

Said plainly.

Fixed price, fixed scope.

The proposal lists exactly what's included. If we underestimated, that's our problem — the price stands.

You own everything.

Code, prompts, configs, docs, credentials. Transferred at handover, no license strings attached.

Senior engineers only.

The people in the kickoff call are the people doing the work. No bait-and-switch to juniors.

30 days of fixes.

Anything we built that breaks or misbehaves in the first 30 days after launch, we fix free.

Weekly visibility.

Demos and honest status every week. If we're behind, you'll hear it from us first.

Process questions

Asked about how we work.

A one-week engagement: we interview the people doing the work, shadow one or two real workflow cycles, inventory your tools, and measure where time and money actually go. You get a findings document ranked by payback time — and you keep it whether or not we work together.

A typical pilot — a content pipeline, a CI/CD overhaul, a cloud hardening sprint — runs 3–4 weeks from kickoff. Book an audit this week and you'll have a roadmap within 7 days. Dedicated engineers usually embed within 2–3 weeks.

Fixed-scope work has defined acceptance criteria — if we don't meet them, we don't get signed off. Retainers run month to month after an initial 90-day commitment. And because everything is built in your repos and accounts with full documentation, you're never locked in or left with a black box.

Async-first in your Slack or Teams, with a shared board for priorities and weekly demos on your schedule. You'll always know what's done, what's next, and what's blocked — no status-chasing required.

All 14 questions

Start free

Week one costs nothing.

The audit is free, takes a week, and the report is yours to keep. Worst case, you learn exactly where your hours go. Best case, you never do that work manually again.