What shows up in real workflows
This page lists tools, services, and accounts commonly used while testing and running real side gigs.
Some are essential.
Some are situational.
Some were tried and later dropped.
Nothing is listed here unless it has been used or evaluated in a real-world context. Tools may appear or disappear over time as workflows change.
How to Use This Page
This is a reference page, not a recommendation list.
- Inclusion does not mean a tool is right for you
- Absence does not mean a tool is bad
- Tools stay listed only while they remain relevant
If a tool creates more friction than it removes, it does not stay.
Core Tools
These are tools that tend to appear across many side gigs, regardless of category.
Web Hosting
Used when a side gig involves websites, landing pages, or long-term assets.
- DreamHost
Used for simple site hosting and long-running projects where stability matters more than speed experiments. - Hostinger
Evaluated for low-cost hosting and fast setup when testing new ideas or smaller sites.
Hosting is infrastructure. It does not create income by itself.
Financial Tracking and Accounts
Used to keep money visible and separate.
- QuickBooks
Used to track income and expenses once activity moves beyond casual experimentation. - Business checking account
Used to separate side gig activity from personal spending once money starts moving consistently.
The goal here is clarity, not complexity.
Supporting Tools
These tools appear in specific situations but are not required for most side gigs.
They tend to solve narrow problems or show up during certain phases.
Payment and Access
Used when platforms or clients require structured payouts.
- Platform payout dashboards
Used to monitor pending balances and timing rather than relying on memory or assumptions.
Operations and Workflow
Used to reduce friction once repetition exists.
- Basic document tools
Used for invoices, notes, and simple tracking before anything more complex is justified.
Tools in this category are often dropped or replaced as needs change.
Tools by Use Case
Some people prefer to think in functions rather than tool names.
Common use cases include:
- Tracking income and expenses
- Managing access and payouts
- Running simple web properties
- Handling basic operations and documentation
A single tool may serve more than one purpose depending on the gig.
Reviews and Deeper Notes
Some tools warrant deeper coverage when:
- Cost is meaningful
- Setup friction is non-trivial
- Marketing claims differ from real-world use
When that happens, the tool links to a dedicated page with:
- What was tested
- What worked
- What didn’t
- Why it stayed or was dropped
If a tool does not link out, that is intentional.
Expectation Reset
Tools do not create income.
They:
- Reduce friction
- Improve visibility
- Save time once work already exists
Buying tools before doing the work is one of the most common failure modes.
This page exists to document what earns its place, not to encourage shopping.
Where This Fits in the System
This page supports:
- Side gig evaluation and testing
/side-gigs/ - Method-based decision making
/the-abc-eflow-method/
It is a reference layer, not a starting point.
Final note
If a tool is listed here, it was used or evaluated.
If it stops being useful, it leaves.
That rule matters more than completeness.
Some links on this page may be affiliate links. They do not affect what gets listed or how tools are described.