Systems practice

  • Selected commissions and labelled concepts

Practical workflow support for the repetitive parts of creative and operational work.

I map repetitive work into clear inputs, decisions and outputs, then shape lightweight tools or workflow structures that keep human review central.

Current focus

Clear inputs, repeatable steps and useful outputs.

The best opportunities are practical workflows where people still make the decisions, but the repetitive structure becomes easier to manage.

Selected commissions and labelled concepts

Workflow automation and lightweight tools

Practical automation thinking for structured workflows, small internal tools and clearly labelled concepts.

Concept workflow

Deterministic front-end demonstration

From inquiry to reviewed next steps.

Watch a generic request become structured fields, a routing decision, prepared outputs and a final human review.

A cinematic front-end concept: no live AI, backend, database or external action is implied.

Deterministic front-end demonstration — no live AI, backend or database.

Static workflow summary

Structure first. Automation only where it supports review.

  1. Input brief A generic inquiry becomes the source material.
  2. Field extraction Relevant details separate from the open text.
  3. Decision / routing Simple process logic chooses the preparation route.
  4. Structured lead The request resolves into a concise lead summary.
  5. Checklist / preparation Unknowns become a practical preparation list.
  6. Draft response A response structure is drafted, not sent.
  7. Follow-up action The next internal actions stay visible.
  8. Human review / approval A person reviews everything before external action.

From inquiry to reviewed next steps.

Concept workflow

Opening frame

Deterministic front-end demonstration

From inquiry to reviewed next steps.

Deterministic front-end demonstration — no live AI, backend or database.

Example inquiry

Hi, I need new photos and a small website page for a construction project. We have a rough deadline next month and want to know what information you need first.

Extracted fields

  • Project type: construction
  • Services: photography + web page
  • Timing: next month
  • Missing info: scope, location, usage

Routing decision

  • Photo + Web
  • Needs clarification
  • Prepare intake

03 · Prepared outputs

Lead summary

  • Construction project
  • Photography + website page
  • Timing: next month
  • Unknowns: scope, location, usage

04 · Prepared outputs

Checklist

  • Confirm location
  • Confirm deadline
  • Define image usage
  • List website sections
  • Prepare quote context

05 · Prepared outputs

Draft response

  • Draft only — not sent automatically
  • Thank the requester
  • Ask for missing details
  • Explain the next step

06 · Prepared outputs

Follow-up

  • Request missing information
  • Prepare proposal context
  • Review before external action

07 · Prepared outputs

Human review

  • Human review required
  • No external action happens automatically

Deterministic front-end demonstration — no live AI, backend or database.

  1. Input brief
  2. Field extraction
  3. Decision / routing
  4. Structured lead
  5. Checklist / preparation
  6. Draft response
  7. Follow-up action
  8. Human review / approval

Focus

Where automation can help.

The work starts with the process before the tool: what comes in, what needs to be decided, what needs to be created and what still needs human review.

  • Intake structuring for project requests or recurring briefs.
  • Checklists and follow-up flows for repeated work.
  • Document, spreadsheet or data transformation for internal use.
  • Lightweight internal tools that support admin rather than replacing judgement.

Keep exploring

Workflow opportunity

Have a repetitive workflow that needs structure?

Tell me what comes in, what has to happen next and where the friction sits. I will help identify a practical first step.

Discuss a workflow

Useful details: current tools, example inputs, repeated steps and desired output.