How an engagement runs, from first call to delivery
Every engagement starts the same way: a short call and terms agreed in writing before anything is charged. After that, the steps depend on what you need: engineers in your team, one workflow automated, a failing system fixed, or a first release built.
Organizations we’ve worked with
- Airbnb
- TheAMLab
- Hood
- NAMA
- Klaro
- GoBoon
- Studio Arlington
Four things that never change
Whichever way you start, this is how the work is run.
Tell us what’s holding the work up
Send a few lines through the contact form or book a 20–30 minute call. We reply within 4 working hours, or the next working morning (Pakistan time).
Agree it in writing
Before any paid work: the engineer and trial task, or the scope, price and the checklist the work must pass. Nothing is charged until you approve.
Delivered in your systems
We work in your repo and your accounts, test against what was agreed, and the work stays yours.
Covered after go-live
Each offer states its cover: 30 days of defect fixes after an MVP launch, two weeks watching live runs on Production-tier Sprints and up, an optional Care plan after a repair.
Pick your situation, see the steps
Each way of working has its own first step, timeline and price.
from $1,900/mo
Engineering Capacity
You meet the engineer and agree how the week will be judged before anything starts.
- 01
Backlog call
30 minWalk us through your backlog, stack and hours. We check there is ongoing work, the rate fits, and someone can review the engineer. Then we propose an engineer and a task sized for a week.
- 02
Meet your engineer
Short callA call with the proposed engineer. We confirm their skills, hours and responsibilities in writing, so you know who will access your systems.
- 03
Free trial week
5 working daysWith access and a reviewer ready on day one, they work on the task in your repo under NDA. You keep the work either way.
- 04
Review, then monthly
End of weekOn day five we review technical quality, communication and working fit together. Paid work starts only when you approve it in writing.
from $750
Automation Sprint
Four steps, one fixed price, one workflow running in production.
- 01
Define
Day 1–2We map the trigger, systems, rules and edge cases, then send a written scope, fixed price and the checklist it must pass.
- 02
Build
Week 1We build in your accounts, with progress updates as it takes shape.
- 03
Verify
Before go-liveWe run the agreed test cases, including the awkward ones. You sign off against the checklist.
- 04
Stabilize
After go-liveWe fix what fails the checklist; Production and up adds two weeks of watching live runs.
Workflow fixes $249 · Apps quoted
System Rescue
From a free 20-minute triage call to a fix with a warranty. Nothing is charged until you agree in writing.
- 01
Triage call
Free · 20 minTell us what is failing, since when and which tools are involved. We confirm whether it qualifies for a workflow Quick Fix, needs a diagnostic, or can be scoped for a quoted app or broader repair.
- 02
Diagnose
1–2 business daysWhen agreed for an unclear app or integration failure, we trace the affected journey and send written findings, open dependencies and repair options.
- 03
Repair
Quick Fix or quotedWe fix the cause once access is in place. Most Quick Fixes take 2 business days; a larger repair follows its quote.
- 04
Keep it fixed
OptionalA Care plan can watch the covered workflows after the fix.
Fixed quote
MVP Build
One delivery lead throughout, regular demos, and a decision point before each payment.
- 01
Scope
Free, or a 3–5 day Scope SprintWe fix the core journey, features, exclusions, dependencies, acceptance criteria, build plan and schedule in writing.
- 02
Design
Early buildUX for the core journey, reviewed with you before the screens are engineered.
- 03
Build
Most of the timelineFrontend, backend and integrations, demoed regularly. The core journey is shown working on staging.
- 04
Verify
Before launchWe test the agreed critical paths, then you review against the written acceptance criteria.
- 05
Launch
+30 daysDeployed in your accounts with monitoring and handover. We fix defects for 30 days after launch.
Who owns what
Octacer owns
- Engineering and delivery against the agreed task or written scope
- Testing against the agreed checklist or acceptance criteria
- Progress updates and demos while the work takes shape
- Fixes after go-live, as each offer states
You own
- Access to the repo, accounts and systems involved
- Someone who can review the work and make decisions
- Business rules, edge cases and sign-off
- Your code, accounts and systems, before and after
Ask us on a short call
Tell us what's holding the work up. In 20–30 minutes we say whether we can help and which engagement fits. No preparation needed.