Projects is where ABC-eFlow keeps the work behind the advice visible. Some of these are active websites. Some are operating experiments. Some are older projects preserved because the numbers or mistakes still teach something useful. A few are examples of what happens when a theoretically simple idea develops enough moving parts to qualify for its own weather system.
This is not a polished portfolio page built to imply that every project became a thriving business. The useful part is the variation. Different projects expose different constraints: search demand, content maintenance, vehicle costs, inventory, customer trust, technical debt, household time, capital, skill, and the point where continuing stops being rational.
How to Use the Project Library
Projects are the evidence inventory. Lessons From the Field is the interpretation layer. A project page tells you what was built or tried. A field note pulls out the lesson that can improve another decision.
If you are comparing a general idea, start with the relevant Build, Run, Fix, or Earn page. Come here when you want to see a real example behind the framework. If you are more interested in the lesson than the project itself, go to Lessons From the Field.
Content Sites and Digital Properties
ABC-eFlow
ABC-eFlow is both the framework site and a live case study in its own right. It started as a side-gig resource and evolved into a broader small-operator systems site after the work revealed stronger needs around Build, Run, Fix, Earn, and real project evidence. Its own cleanup, positioning changes, internal-link work, media systems, monetization, and search results are part of the project.
Humidity at Home
Humidity at Home is a residential humidity content property built around practical homeowner search problems. It is useful as a case study because the work includes content architecture, product fit, affiliate monetization, image systems, search indexing, page differentiation, and the slow accumulation of traffic rather than a launch-day spike.
GF Travellers
GF Travellers focuses on the practical problem of eating gluten-free while traveling. The project is a good example of trust-sensitive content where the reader is not looking for generic inspiration. They need useful decision support around cuisines, destinations, transit, cross-contact, and situations where the answer may be "this is harder than it looks."
Unsettled Man
Unsettled Man is a long-form content project built around responsibility, maturity, relationships, values, and practical reflection. It is a different editorial model from the utility-heavy ABC-eFlow and Humidity at Home sites, which makes it useful for comparing voice-driven authority with search-driven problem solving.
Business and Expertise Experiments
Grey Wolf Grooming
Grey Wolf Grooming is a product-brand experiment that became a useful lesson in ecommerce friction, inventory risk, branding, product economics, and the difference between liking a concept and wanting to operate the machine required to support it. A paused project can still have a perfectly good return if the lesson prevents a larger mistake later.
Grey Wolf Resources
Grey Wolf Resources represents expertise-based work rather than a consumer content site. The project centers on technical research, executive briefings, cybersecurity and compliance framing, white papers, and the problem of turning experienced judgment into a useful deliverable without inflating it into consultant theater.
Projects With Hard Numbers
Uber Driving in Practice
The Uber project is one of the clearest examples of why gross revenue is not the same as practical return. The underlying real-numbers article tracks 308 trips, mileage, gross revenue, time, and estimated costs from a rural starting point. It is useful because the experience is neither "rideshare is a scam" nor "drive whenever you want and print money." The answer depends on the operating context.
Living in Fixer-Uppers
Living in fixer-uppers is not a side-gig case. It is a longer-term wealth-building pattern involving housing decisions, renovation work, market appreciation, mortgage paydown, sweat equity, and the cost of living inside the project while it is being improved. That makes it useful precisely because it does not fit neatly into the side-hustle box.
Projects That Started Before "Side Gig" Was a Phrase
The Garage Table Empire
The Garage Table Empire looks back at childhood resale, tiny margins, garage-sale arbitrage, bubble gum money, pinball, and the early discovery that buying something cheap is not the same as having a buyer. It is deliberately lighter than the other project pages, but the underlying lesson about demand, inventory, and cash conversion survived just fine.
Commodore 64 Restoration
The Commodore 64 restoration project combined repair skills, sourcing, testing, bundling, resale, nostalgia, and hundreds of hours of labor. The gross numbers can look respectable until the time is counted. That makes it a useful example of experience-based work where the project may be worthwhile for reasons that extend beyond the hourly return.
What These Projects Have in Common
The projects are different, but the operating questions repeat. What did we assume? What was the real starting point? Which constraint dominated? Where did the money, time, attention, and risk actually flow? What evidence would justify doing more? What would justify stopping? Those are the same questions used in the ABC-eFlow Method.
The answer is not always revenue. A project can produce a reusable skill, a body of evidence, a durable content asset, a better operating system, or a clear reason not to repeat the experiment. The point is to record the actual return instead of rewriting the story later so every project looks intentional.
Why the Messy Middle Stays Visible
A finished case study tells you what survived. A working project tells you what went wrong on Tuesday. Both are useful, but the second one is where a lot of transferable knowledge lives: traffic that arrived from an unexpected page, affiliate clicks damaged during cleanup, tools that added more work than they removed, a site architecture that became too narrow, or a project that needed a different definition of success.
That is why this section connects directly to Lessons From the Field. Projects are the inventory. Field Notes are the observations. Neither needs every story to end with a trophy.