Nine public repositories can cover a surprising amount of business infrastructure: analytics, search research, invoicing, booking, billing, forms, CRM, marketing automation, and customer support. In Andrew Warner's walkthrough, each tool has two angles: use it to improve your own operation, or package implementation and ongoing support for a client. The companion slide deck adds screenshots, vendor links, and sample offers.
A GitHub repository is not a revenue stream by itself. The sellable work is selecting the right tool, deploying it safely, connecting the data, training people, and proving an outcome. Also, “public code,” “open source,” “self-hosted,” and “free to operate” are not synonyms. License and production-readiness checks matter before a client relies on any of these systems.
Watch Andrew's Walkthrough
Credit: The Next New Thing episode, published 29 September 2026. The repo examples and sample consulting offers come from Andrew and his slide deck. Product caveats below were checked against current project documentation on 30 September 2026. The episode includes a separate Zapier sponsorship.
The Nine-Tool Map
| Tool | Business job | First useful test | Video |
|---|---|---|---|
| 1. PostHog | Product analytics | Instrument one conversion funnel, review consented session replays, and test one change against a baseline. | Watch chapter |
| 2. OpenSEO | SEO research and audits | Track a focused keyword set, connect Search Console, inspect a technical audit, and put changes into a prioritized work queue. | Watch chapter |
| 3. Invoice Ninja | Quotes, invoices, and payments | Move one quote-to-payment flow into a client portal with reminders and a reconciled payment test. | Watch chapter |
| 4. Cal.diy | Scheduling | Test one booking type with calendar conflict checks, reminders, cancellation rules, and a payment flow if needed. | Watch chapter |
| 5. Autumn | Pricing and billing logic | Model a free trial, one paid plan, and usage overages before wiring billing events into the product. | Watch chapter |
| 6. Typebot | Conversational forms | Replace one long form with a branching intake conversation and measure completion and lead quality. | Watch chapter |
| 7. Frappe CRM | Lead and deal management | Put one team’s lead stages, activity history, ownership, and follow-up rules into a shared pipeline. | Watch chapter |
| 8. Mautic | Marketing automation | Build one permission-based follow-up sequence with a clear unsubscribe and a measurable conversion goal. | Watch chapter |
| 9. Chatwoot | Customer support inbox | Unify two customer channels, set routing and response ownership, and measure first-response time. | Watch chapter |
These nine are different layers, not nine interchangeable alternatives to one paid app. A small service firm might begin with a booking page and invoices; a software company might begin with event analytics and usage billing. Do not install the entire stack because a list made it look attractive.
Every Repository, in Video Order
1. PostHog Product analytics
Use it in your business: Instrument one conversion funnel, review consented session replays, and test one change against a baseline.
Potential client offer: A conversion-leak audit with tracking setup, an annotated funnel, and a 30-day experiment report.
Check before deploying: PostHog says self-hosting is officially unsupported and places scaling, upgrades, security, and recovery on the operator.
2. OpenSEO SEO research and audits
Use it in your business: Track a focused keyword set, connect Search Console, inspect a technical audit, and put changes into a prioritized work queue.
Potential client offer: A recurring SEO scorecard that includes interpretation and approved fixes, rather than a raw automated report.
Check before deploying: Check data-provider credits, API keys, Cloudflare limits, and the quality of the underlying search data before promising a free replacement for a paid suite.
3. Invoice Ninja Quotes, invoices, and payments
Use it in your business: Move one quote-to-payment flow into a client portal with reminders and a reconciled payment test.
Potential client offer: Set up a small service business’s invoicing, recurring plans, templates, and staff handoff.
Check before deploying: The repository calls itself source-available, not simply open source. Review its license, client-facing branding terms, payment fees, tax handling, and backups.
4. Cal.diy Scheduling
Use it in your business: Test one booking type with calendar conflict checks, reminders, cancellation rules, and a payment flow if needed.
Potential client offer: Build a paid-consultation booking flow and measure completed bookings and no-shows.
Check before deploying: The project README recommends Cal.diy for personal, non-production use; commercial teams should evaluate Cal.com or another supported option.
5. Autumn Pricing and billing logic
Use it in your business: Model a free trial, one paid plan, and usage overages before wiring billing events into the product.
Potential client offer: Design and implement subscriptions or AI-credit metering for a SaaS team, including test invoices and exception paths.
Check before deploying: Autumn sits on top of Stripe and other services. Test webhooks, tax treatment, failed payments, ledger accuracy, and the full running cost.
6. Typebot Conversational forms
Use it in your business: Replace one long form with a branching intake conversation and measure completion and lead quality.
Potential client offer: Create a product-finder or lead-qualification flow with consent, CRM handoff, and weekly conversion review.
Check before deploying: Typebot uses FSL-1.1-Apache-2.0, which restricts competing commercial services for current versions. Review the license before white-labeling or resale.
7. Frappe CRM Lead and deal management
Use it in your business: Put one team’s lead stages, activity history, ownership, and follow-up rules into a shared pipeline.
Potential client offer: Migrate a small sales team from spreadsheets or a seat-priced CRM with a documented process and training.
Check before deploying: Migration quality, contact permissions, email and telephony integrations, and the AGPL-3.0 license need review.
8. Mautic Marketing automation
Use it in your business: Build one permission-based follow-up sequence with a clear unsubscribe and a measurable conversion goal.
Potential client offer: Create onboarding or reactivation campaigns, including list hygiene, deliverability checks, and reporting.
Check before deploying: Mautic is GPL-3.0; hosting, sending infrastructure, suppression lists, privacy compliance, and deliverability still need owners.
9. Chatwoot Customer support inbox
Use it in your business: Unify two customer channels, set routing and response ownership, and measure first-response time.
Potential client offer: Set up a support inbox and a narrowly scoped order-status assistant with clear human handoff.
Check before deploying: Self-hosting requires a maintained server, backups, channel integrations, and careful review of what AI features are available on the chosen edition.
The Zapier Interlude Is Not a Tenth Repo
At 09:45, Andrew pauses for the sponsor's Next-Gen Zaps segment. The pitch is to let deterministic steps run as code and reserve AI for judgment. Treat the claimed cost reduction as Zapier's example, not a universal result. See the sponsor slide, Wade Foster's X announcement, and Zapier waitlist. Zapier is neither self-hosted nor one of the nine repositories.
Free Code Is Not a Free Production System
The deck compares paid-plan sticker prices with code you can run yourself. That is useful for spotting opportunities, but not a like-for-like total-cost comparison. Before replacing a working vendor, account for cloud hosting, operations, storage, data API credits, payment and messaging fees, security maintenance, migrations, training, and support. Also check which features exist in the community edition rather than assuming the hosted product and repository are identical.
- License first: Invoice Ninja calls itself source-available; Typebot's Functional Source License restricts competing services. Frappe CRM uses AGPL-3.0, while Mautic uses GPL-3.0. Check the current file for the version deployed.
- Support boundary: PostHog's self-hosting guidance says that route is not officially supported and puts maintenance risk on the operator. Cal.diy's README explicitly recommends personal, non-production use.
- Data and delivery: OpenSEO still needs reliable search data; Mautic needs email delivery; Autumn needs payment infrastructure; Chatwoot needs integrations and staff ownership. Test the entire workflow, not just the dashboard.
This is an operational checklist, not legal advice. Read the relevant licenses and current vendor terms before modifying, reselling, or white-labeling a deployment.
Start With One Paid Pilot
- Choose a visible business problem: lost checkout conversions, an unworked lead queue, unpaid invoices, missed bookings, or slow customer replies.
- Define one baseline and one acceptance measure, such as completed booking rate, first-response time, or invoices paid within 14 days.
- Deploy a test environment, review license and security posture, and connect only the data required for the pilot.
- Run a small workflow with a named human owner and a rollback plan. Show the client the result before selling an ongoing subscription.
- Price setup, migration, monitoring, training, and support separately. Do not promise Andrew's example fees as a guaranteed market rate.
Jump to a Tool in the Video
| Time | Section | Time | Section |
|---|---|---|---|
| 00:00 | Why these repos matter | 00:18 | PostHog |
| 02:51 | OpenSEO | 06:09 | Invoice Ninja |
| 09:45 | Zapier sponsor | 11:15 | Cal.diy |
| 14:15 | Autumn | 16:57 | Typebot |
| 20:15 | Frappe CRM | 22:21 | Mautic |
| 24:45 | Chatwoot |
Source and Link Map
Andrew Warner's original episode and the companion presentation are the two starting points. The presentation provides screenshots, comparisons, and the one X announcement linked above; it does not provide separate playable videos for all nine tools. The episode's chapter links are therefore the video route for each repo. Each numbered entry above includes its GitHub source, project site, setup documentation, and matching slide.
For related local guides, see our repo-to-service breakdown and OpenSEO walkthrough. These help turn a promising repo into a bounded, reviewable delivery rather than an unsupervised installation.