Jeremy Reevese

Posted on Nov 14

My One-Person Company Automation Stack (2025 Edition)

#python #notion #automation #productivity

How I automate my life, my work, and my one-person company using Python, Notion, GitHub, and no-code tools.

Running a one-person company means wearing all the hats —

engineering, project management, documentation, business ops, invoicing, marketing, client support…

But here’s the secret:

If I can't automate it, I don't scale it.
If I can automate it, I turn it into a system.

Over time, this principle evolved into a real thing:

my Automation Stack — the infrastructure that keeps my workflow running smoothly without hiring anyone.

In this post, I’ll break down my 2025 automation setup,

from foundational tools to the small scripts that quietly keep the company alive.

1. Core Principles

Before the tools, here are the rules:

1️⃣ Keep it minimal

No complex frameworks. No unnecessary abstractions.

2️⃣ Prefer boring tech

Python requests > five layers of orchestration.

3️⃣ Build for repeatability

Every workflow should be:

Logged
Re-runnable
Portable
Easy to debug

4️⃣ Automate public-first

If I build something useful for myself,

I write about it and turn it into an asset (like this post).

2. My Automation Stack Overview

Here’s the 2025 snapshot of my one-person company's system:

Layer	Tooling	Purpose
Data & Notes	Notion	Source of truth, project logs, planning, daily reports
Automation Scripts	Python + Notion API	Daily report generator, database sync, task pipelines
Workflow Orchestration	n8n / Make.com	Multi-step workflows, API calling, webhook triggers
Infrastructure	GitHub Actions	Scheduled workflows, backups, cron jobs
Knowledge Distribution	Dev.to + Medium + GitHub	Public learning, documentation, portfolio
Client-Facing	Upwork + LinkedIn	Social proof, authority building

Nothing fancy, nothing overengineered —

just tools that carry their weight.

3. Python: The Heart of My Automations

I keep Python scripts extremely small and modular.

💡 My typical script does one thing only:

Write a daily report to Notion
Export Notion → CSV
Sync project tasks
Check deadlines
Push logs to GitHub

Example structure:

automation/
  daily_report.py
  notion_to_csv.py
  sync_projects.py
  utils/
    notion.py
    dates.py
    logger.py

Each file: < 80 lines.

Each script: callable manually, via cron, or via GitHub Actions.

4. Notion as My Internal Database

Notion is my:

CRM
Project tracking
Daily report log
Content pipeline
Idea notebook
Billing record
Knowledge hub

Every API-connected table becomes a “micro-database”.

Typical properties I use:

Name
Status
Created
Updated
Tags
Owner
Priority

Python → Notion API connects EVERYTHING.

5. n8n / Make: Multi-Step Workflow Glue

Not everything needs Python.

Sometimes the fastest solution is no-code automation.

My favorite n8n workflows:

Listen to a webhook → push to Notion
Generate a weekly digest → send to email
Trigger Python scripts via command node
Transform incoming JSON before storage
Sync backups to storage buckets

I treat n8n like a “visual cron + API router”.

6. GitHub Actions as My Scheduler

I don’t use cron on local machines.

Instead, I use GitHub Actions to run workflow scripts.

Common automations:

Daily report generator (9:00)
Notion → CSV backup (midnight)
Weekly summary pipeline (Friday)
Push logs to GitHub repo daily

Example workflow:

name: Daily Report
on:
  schedule:
    - cron: "0 1 * * *"
jobs:
  run:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v4
        with:
          python-version: '3.11'
      - run: pip install -r requirements.txt
      - run: python automation/daily_report.py

This alone is worth hours every week.

7. What This Stack Enables

⏱️ Time saved per day:

~1–2 hours

💼 Tasks automated:

Daily logs
Data exporting
Progress tracking
Task sorting
Content scheduling
Personal analytics
Client-related paperwork

📈 Business benefits:

More time for deep work
More content output
More proof-of-work for clients
More reproducible workflows
A more valuable portfolio

8. Why This Works for a One-Person Company

Because the entire stack is:

✔ Cheap

Most of it is free.

✔ Simple

Small tools that fit together.

✔ Portable

You can move everything to another platform in one weekend.

✔ Easy to teach

Clients love simple systems.

✔ "Hireless"

Automation is your employee.

This is exactly why I chose this tech stack instead of chasing shiny tools.

9. What’s Coming Next (Open Roadmap)

I'm expanding this stack in 2026–2027 with:

FastAPI microservices
LangChain for internal knowledge agents
A personal “Ops Dashboard” built on Notion
Automated content distribution pipelines
A GitHub-hosted data lake
Client-ready automation templates

If you’re curious about any of these, leave a comment and I’ll build the tutorial.

10. Final Thoughts

Running a one-person company feels intimidating.

But once you build the right systems, everything becomes lighter:

Less chaos
More clarity
More output
More opportunities

Automation isn’t about replacing yourself —

it’s about making space to do the real work.

If you want breakdowns of any script or workflow in this post,

tell me which one — I’ll write it.

DEV Community