Repetitive handling
The same files and fields need attention, every single time.
Independent engineer · San Francisco
Turn repetitive work into reliable software.
I help operations teams at growing companies replace manual document and data workflows with dependable automation and integrations.
The everyday inputs
- PDFs
- CSV
- API
Files, inboxes, and apps.
One clear workflow.
- Read the inputs
- Check the details
- Route the result
Human review where it matters.
Ready for the next step
- Clean data
- The right action
- A clear record
Less work between the systems.
- Clear scope
- Verified behavior
- Observable failures
- Documented handoff
Typical problems
Too much work happens between the tools.
Inboxes, files, and spreadsheets keep work moving. The manual handoffs between them are where things get stuck.
Disconnected data
People copy and reconcile information between tools that don't connect.
Invisible failures
A missed file or failed job goes unnoticed until the next step stalls.
Services
Focused software.
Useful every day.
Workflow Automation
Give repeated work a clear path from incoming document to completed task.
- document-processing workflows
- scheduled jobs
- operational utilities
- validation and exception routing
- focused internal tools
Data & API Integrations
Keep information moving between the systems your team already uses.
- API and SaaS integrations
- ingestion and synchronization
- transformation and reconciliation
- data-quality checks
- reliable system handoffs
Not every workflow needs AI. Where unstructured content calls for it, a focused AI prototype can help test what is useful.
Approach
A clear path from idea to handoff.
Quality is part of the build: explicit boundaries, input validation, automated tests, useful logs, a recovery path, and clear documentation.
Understand
Map one workflow, where it gets stuck, and what a useful result looks like.
Design
Agree on scope, system boundaries, and how the result will be tested.
Build
Connect the necessary tools and build the smallest useful version first.
Verify
Check normal and failure cases, then document how to run and maintain it.
About
Work directly with the person building it.
I'm Andrey Kutsenko, a software engineer in San Francisco. My background includes data parsing, document-processing pipelines, Unix/Linux automation, operational tooling, and software quality.
Simple Process is my independent engineering practice, focused on the everyday work that software can make simpler.
FAQ
A few practical questions.
What kinds of workflows are a good fit?
Repeated document or data tasks with clear inputs and outputs. A good starting point is a narrow process where people copy, check, or move the same information regularly.
Do you replace the tools we already use?
Usually not. A focused integration or internal tool is often more useful than replacing an entire working system.
How does a project begin?
Tell me about one workflow and what tends to go wrong. Together we define success and choose an appropriate discovery, prototype, or implementation scope.
Who will I work with?
You work directly with me, Andrey Kutsenko, from the first conversation through design, implementation, and handoff.
Let’s make it work
What workflow does your team keep doing by hand?
Tell me about the inputs, the repeated steps, the tools involved, and what tends to go wrong. I'll reply personally and tell you whether it looks like a good fit.
One workflow is a good place to start.