Delivery process

How we work

Every AutoProbaho engagement — from a garments factory in Bangladesh to a Mittelstand company in Germany — follows the same five phases. Each phase has a fixed scope, a written deliverable and a review with you before the next one starts — so you always know what you are paying for and what comes next.

Engagement simulator

Choose the situation closest to yours to see which phase we would start with and how the collaboration typically runs.

Where are you starting from?

Recommended first phase

Process audit, then one core module

When data lives in spreadsheets and chats, the biggest risk is building the wrong thing. A short audit maps how orders, stock and money actually flow, then we build the single module that removes the most re-typing — usually inventory, sales or customer management.

Typical cadence

  • Discovery workshops with the people doing the work
  • Weekly written update: done / next / needed from you
  • Review of the process map and roadmap before any build starts

What usually follows

Connect accounting and messaging, then automate approvals and reports.

Discuss this starting point

Illustrative scenario (anonymised)

The five phases

The order is deliberate: we do not write software until we understand the process it must serve.

  1. 01

    Audit

    Interviews, process mapping and a review of your current tools and spreadsheets. Output: an audit report with the gaps, quick wins and a recommended first module.

  2. 02

    Build the core system

    Data model, roles and the first module are designed, reviewed with you and built. Output: a working system with real data, user guides and admin access.

  3. 03

    Connect

    Accounting, payments, e-commerce, messaging and existing databases are integrated through APIs and webhooks. Output: data entered once, visible everywhere.

  4. 04

    Automate & AI

    Notifications, approvals, scheduled reports and document handling are automated with n8n; AI steps are added only with human review. Output: fewer manual hand-offs.

  5. 05

    Measure & maintain

    KPI dashboards, monitoring, backups and a support arrangement. Output: evidence that the change works, and a system that keeps working.

Communication cadence

You get one named contact — the founder — and a short written update at the end of every working week: what was done, what is next, what we need from you. Larger decisions are handled in a scheduled review call; small ones over email or WhatsApp, whichever your team already uses.

Requests, bugs and questions are tracked in a shared board you can see at any time. Nothing depends on remembering a chat message.

Fixed-scope phases

Each phase is quoted separately with a written scope: what is included, what is explicitly excluded, the deliverables and the acceptance criteria. Work outside the scope is not started silently — it is written down, estimated and either added to the current phase by agreement or planned for the next one.

This protects both sides. You are never surprised by an invoice, and we are never asked to guess what “done” means. It also lets you stop after any phase with a complete, documented result in hand.

Tooling and hand-over

Code lives in a repository under your account. Documentation — process maps, data model, runbooks, user guides — is written as we go and handed over with the system, not reconstructed at the end. Credentials are stored in a secret manager, never in chat or spreadsheets.

Where possible we build on open, widely used technology (TypeScript, PostgreSQL/SQLite, n8n, Cloudflare) so that any competent developer can maintain the system after us.

Frequently asked questions

It depends on scope, but a first core module typically takes around 8–12 weeks after the audit. We give an indicative range in the proposal and update it after the audit — never a promise before we understand the process.

Start with a conversation, not a contract

In a free 30-minute call we listen to how your business runs today and tell you which phase makes sense first.