All work

Concept project: a sample build that shows how we approach this kind of product. The client, features and figures are illustrative.

Full stack · Python (Django) + React · Business automation · SaaS

flowops

An AI-assisted workflow platform that replaces manual approvals and copy-paste admin with automations anyone can build.

Client
Concept: operations SaaS
Year
2026
Services
Product design, Python backend, React front end, Cloud & DevOps
Live site
Concept build
FlowOps interface

Overview

The brief

Operations teams at growing companies run on a patchwork of email, spreadsheets, chat and five SaaS tools that do not talk to each other. Approvals sit in inboxes, the same data is typed into three systems, and nobody can see where a request is stuck. FlowOps puts every repeatable process into one workspace: a visual builder for workflows, background jobs that run them reliably, and an audit trail that shows who did what and when.

Problems & fixes

What was in the way

Pick a problem to see what was wrong, what we built and what changed.

The problem

Purchase and invoice approvals travelled by email. Requests waited days because nobody knew whose turn it was, and finance chased people by phone.

What we built

Approval steps with named owners, deadlines and escalation. Each request shows its current step, and reminders go out automatically before the deadline passes.

What changed

Every request has a visible owner and status, and overdue approvals escalate on their own.

1 / 4

Impact

What it changed

1,284Workflow runs a day
62%Faster approvals
14Hours of admin saved a week
0Duplicate records from retries
  • One workspace for approvals, automations and their history.
  • Operations staff own their processes instead of waiting on developers.
  • Failed integrations are retried and reported, not discovered at month end.

How it works

Under the hood

Click any part of the system, or play the flow from start to finish.

Step 1 · React · React Flow

Workflow editor

Canvas for triggers, conditions, approvals and actions, with versioning and a dry-run mode.

01 —

No-code builder

Visual workflows with conditions, schedules and approvals, tested before they go live.

02 —

Safe to retry

Idempotent jobs mean a re-run never double-posts an invoice or an order.

03 —

Audit-ready

Every step, change and approval is logged with who did it and when.

Timeline

  1. Weeks 1–2User journeys, workflow model and editor prototype
  2. Weeks 3–5Django API, Celery runner, approvals and roles
  3. Weeks 6–7Integrations, webhooks, dashboard and AI suggestions
  4. Week 8Load tests, AWS deployment and monitoring

Tech stack

PythonDjangoDjango REST FrameworkReactTypeScriptReact FlowPostgreSQLRedisCeleryDockerAWS ECS

got an idea?let's lift it.

Tell us what you're building. A senior engineer, not a salesperson, replies within one business day.

Start a project
Start a project