helplouisget.work

Practical systems for teams buried in manual work

I build automation, data workflows, and internal tools that help teams move faster.

I help operations and data teams reduce copy-pasting, clean up messy reporting, and turn fragile workflows into systems people can actually trust.

View Resume Contact Me

Built across operations, recruitment, training, and market research workflows.

The problem most teams already feel

Important work gets buried in busywork.

The pain usually does not look dramatic from the outside. It looks like "just one more spreadsheet," "just double-check it," or "we'll fix it later." Then the reporting slows down, trust drops, and small mistakes keep multiplying.

copy, paste, repeat

Too much copy-pasting

People keep moving the same data between sheets, forms, dashboards, and messages by hand.

Messy spreadsheets

Versions drift, formulas break, and only one person knows why the numbers changed.

Human error

A small admin mistake upstream turns into hours of cleanup downstream. Teams end up double-checking everything because the process itself is not trustworthy yet.

small mistakes, big impact

Slow reporting

Simple questions take too long to answer because the data is scattered and manual to prepare.

The shift I try to create

From scattered and slow to connected and clear.

Good systems do not just save time. They reduce doubt. They make reporting less fragile, handoffs less painful, and decisions faster to act on.

Lightweight

Simple to use. Easy to maintain.

Reliable

Built with guardrails and data quality in mind.

Impactful

Faster cycles, clear insights, better decisions.

Messy inputs

Spreadsheets
Forms
Databases
Emails
Web data
Automations & Data Workflows Clean. Connect. Transform.

Useful outputs

Dashboards
Reports
Alerts
Internal tools
Data you can trust

fewer handoffs, fewer surprises.

Map the real workflow

Start with where work actually gets stuck, not where the spreadsheet happens to end.

Automate the repetitive parts

Pull data, move files, trigger updates, and remove the handoffs that eat time every week.

Validate the data

Add checks so the team can trust the output instead of rechecking everything manually.

Ship something people use

Dashboards, tools, and workflows should make daily work calmer, not more complicated.

What I actually build

Useful systems, not just polished diagrams.

I work across operations, data, and AI-assisted workflow support.

The mini panels below are simplified sketches of real workflows I have shipped — not literal screenshots of client systems.

Workflow automation

n8n, Apps Script, and Python workflows that remove repetitive busywork and keep teams moving.

Syllabus Generate SCORM
  • Triggers and routing
  • Batch operations
  • Alerts and handoffs

Data pipelines and reporting

Collection, cleaning, transformation, and reporting flows that turn scattered inputs into useful decisions.

Extraction runsrecords
Job orders — regional126,048
Job orders — Indonesia13,570
Syllabus library25,000+
  • Scraping and extraction
  • Dataset cleanup
  • Dashboard-ready outputs

Internal tools

Practical tools for operations teams: the kind people open because they save time immediately.

Pull applicationsAuto
Save CVs to DriveDone
AI screen vs criteria3 flagged
  • Ops dashboards
  • Recruitment helpers
  • Team-facing utilities

Careful AI-enabled workflows

AI where it removes friction or speeds up review work, with the human still in the loop.

  • Screening
  • Summaries
  • Triage
  • Screening support
  • Summaries
  • Classification and triage

Proof that the work holds up

Real outcomes. Real operational relief.

The numbers matter because they came from work that had to function in real teams, not from showcase demos built only to look impressive.

Course generation, per run

3.5 hours <10 min

A text-based generation automation built on 25,000+ syllabus records. Once it reached production, it supported about 1,000 LMS-ready SCORM courses shipped within 7 days.

Candidate intake, per CV

2–3 min 13–14 sec

A Glints workflow that pulls applications, files CVs to Drive, and pre-screens with AI — handing colleagues back 106–167 minutes on every 60-CV batch.

Better data. Smarter workflows. Measurable results.

Every time.

How I work

Clear process. Close collaboration. Practical results.

I care about systems people can keep using after the first nice demo. That means listening first, documenting enough, and staying focused on the outcome the team actually needs.

Iterate. Improve. Keep it simple.

  1. Listen before solving

    Understand

    I start by learning where the process hurts, who owns it, and what "better" should actually look like.

    Leaves behind A shared definition of better

  2. Make the flow visible

    Design

    Then I sketch the flow, the data shape, the checks, and the simplest toolchain that fits the team.

    Leaves behind A practical route forward

  3. Put the system to work

    Build

    I build the automation, pipeline, tool, or reporting layer with enough clarity that other people can keep using it.

    Leaves behind A working, maintainable system

  4. Stay after launch

    Improve

    After launch, I tighten the rough edges, document what matters, and keep the system useful as the work changes.

    Leaves behind A system that keeps earning trust

A warm desk still-life with a steaming mug, a small plant, a framed note, and a stack of books.
“Good systems don't just save time. They give people room to do meaningful work.”

If your team is tired of fragile manual work

Give the busywork back to the system.

I'm looking for operations, data, automation, and internal-tool roles where practical systems can give people time back.

Read the resume Start the conversation