Most lost jobs are not lost on price. They are lost when nobody follows up clearly and fast — and the fix is a structured quote system on one side, a chat assistant that pulls from it on the other, and a rule that nothing goes out until the owner says send.
A quote is not finished when the number is sent. The sale is usually won or lost in the next three messages: when can you come, what exactly is included, why does it cost that, and can you put it in writing. A contractor who answers those from the truck in two minutes keeps the job. One who answers that night, from memory, with a number that does not match the first one, does not.
Service Pricer and WALO are two products from the same small company — Service Pricer LLC, which operates under the Artificial Mind Hive name — built to split that problem in half. Service Pricer keeps the structured truth: the price, the customer, the tiers, the job notes, the status. WALO is the assistant the owner texts on WhatsApp; it reads from Service Pricer, drafts the message, shows the owner the move, and acts only on a yes. The current short version of this article called it the point where "the topic stops being theory." This is the long version, with the screens, the plumbing, and the parts that are still in progress.
Nothing Unseen and both products share a publisher. The rule, as always on NU, is receipts: everything here is from the live sites, their public FAQ and integration pages, or the founder's own build record, and anything that is a sample or a work-in-progress is called that.
The WALO homepage on a desktop screen: "Ask once. WALO handles the rest.", the sign-in choices (Google or WhatsApp), and the live app preview in the phone frame.
The problem owners actually have
Here is the version of the problem that owners actually live, not the slide-deck version.
A garage-door company sends a quote on Monday afternoon: $2,900 for a new opener, hinges and rollers. The homeowner reads it, likes it, and texts back at 8:50 p.m.: "Does that include haul-away? And can you do Thursday?" The owner is at his kid's game. He sees the text, means to answer, and answers at 7:10 the next morning — ten hours later. By then the homeowner's brother-in-law has recommended someone else, and that someone else said "yes, Thursday" at 9:05 the night before.
Nothing about the price was wrong. The follow-up was slow and the answer, when it came, was vague ("yeah should be fine, let me check the schedule"). The Harvard Business Review's 2011 study on this, "The Short Life of Online Sales Leads," found that firms which reached a prospect within an hour of a query were nearly seven times as likely to qualify that lead as firms that waited even one hour more. The study was about web leads; the mechanism — the customer's attention decays by the hour — is the same for a quote follow-up.
The second version of the problem is the owner who does follow up, but from memory. He texts "that's $2,900 like I said" when the quote actually said $2,903.19 with a 10% bundle discount and a five-year warranty, and the homeowner, now holding two different numbers, asks for it in writing. The third version is the one where the owner follows up perfectly, wins the job, and then never schedules the next follow-up: the review request, the six-month tune-up, the "your warranty is up next month" note. Each of those is a job that paid once instead of twice or three times.
And underneath all of it is the admin reality: the owner is on a ladder, his phone is his office, and every tool that wants him to open a laptop and log in is a tool he will use on Sunday night, which is too late.
How the industry handles it today
The field-service suites handle follow-up with built-in texting and email, usually templated, usually from a desktop or a dedicated app. Jobber publishes plans from $29 a month with additional users at $29 each; Housecall Pro from $59 a month billed annually; ServiceTitan prices by sales conversation. They work. They also assume a dispatcher.
The small-shop stack is a quote PDF, text messages from the owner's personal number, and whatever reminders the owner sets for himself. Reviews are handled by remembering to ask, which means they are not handled.
WhatsApp, which most of the world's customers already have open, comes with rules a business has to understand before building on it. Meta's WhatsApp Business Platform documentation defines a 24-hour customer service window: when a customer messages a business, a 24-hour timer starts, and it resets every time the customer messages again. Inside that window the business may send free-form messages — text, images, whatever the conversation needs. Outside it, the business may only send pre-approved message templates, which Meta reviews and categorizes (marketing, utility, authentication). Meta's pricing page describes per-message pricing by category, notes free allowances for service messages and entry-point conversations, and warns that pricing updates took effect October 1, 2026. Twilio's WhatsApp key-concepts guide says the same thing in plainer English: free-form inside the 24-hour window, approved templates outside it, and "appointment reminders, follow-ups after the 24-hour window" are the canonical template use case.
Reviews have rules too. Google's business guidance is to request reviews with a link or QR code, to reply to them promptly, and to value negative ones; its contribution policy forbids incentives, discouraging negative reviews, or selectively soliciting positive ones. Yelp's support page on responding to reviews explains that owners respond through their business account, publicly or by direct message — there is no third-party posting lane, which matters for what WALO can and cannot automate. And the FTC's Consumer Reviews and Testimonials Rule, effective October 21, 2024, makes fake reviews and certain review-suppression practices a federal matter.
So "just text the customer back" turns out to have a specification: be fast, be exact, obey the 24-hour window, never post a review on anyone's behalf, and keep the record. That specification is what the Service Pricer and WALO pairing is built against.
How Service Pricer and WALO do it
The division of labor is simple to state. Service Pricer owns the structured data and the customer-facing documents. WALO owns the conversation with the owner, and reads from Service Pricer rather than guessing. The loop, in the words of the current short version of this article, is Pull → Draft → Explain → Close loop. Below is each step as it exists on the live products.
Pull: WALO reads the real quote state
On the Service Pricer landing page, the section headed "Run your quotes from WhatsApp" lists three things WALO can do with a connected account: see recent quotes and invoices, draft a Good/Better/Best quote by text, and send quotes and invoices to the customer. The sample exchange is "quotes this week?" answered by "3 sent · 1 won · Jordan Rivera paid $2,611."
The Service Pricer site's WALO lane at phone width. The capabilities listed are backed by a real callback from WALO into the owner's Service Pricer account.
The part that makes this more than a mock-up is that WALO's assistant has no quote data of its own. When an owner asks about quotes, the WALO bridge calls back into Service Pricer's own endpoint for that owner's account and answers from what comes back. WALO's public FAQ says it from the other side: "if you use Service Pricer, text quotes or invoices and WALO shows your recent ones with links to view, resend, or edit." Service Pricer is, as of this writing, the one business app the WALO bridge has a live-data callback wired for; other apps on the same bridge get the chat but not the lookup until their own callback is added.
That design is the founder's hard line against fabrication. WALO's assistant is under a standing rule that it may not invent facts it cannot look up, and the enforcement is concrete: if an answer contains a phone number that did not appear in the data WALO was given for that turn, the answer is replaced with an honest refusal. That rule came out of a real incident in September 2026 when the assistant made up a business phone number for a user; it has not been allowed to since. For quote follow-up the practical effect is that "what did I quote Maria?" is answered from the quote record or not at all.
Draft: the follow-up written around the structure
The owner texts "draft a follow-up for Maria's quote." WALO has the tier names, the totals, the warranty line and the discount, so the draft can say the true things: three options, the Better one is $2,903.19 with the five-year parts-and-labor warranty, the 10% bundle savings is already in that number, and Thursday is open. The draft goes to the owner, not the customer.
WALO's homepage shows the shape of this in its sample conversation: "draft the email reply and remind me at 2" is answered with "Draft written. Reminder set for 2:00 PM. Nothing sent until you say send." The last sentence is the product's whole posture, and it is on the homepage because the founder wanted it there.
The draft can be aimed at email, text, or a note for a phone call. For email, WALO's FAQ says it "auto-drafts a reply the moment a lead emails," and for owners who connect Gmail the reply can go out from their own address in the same thread. For Yelp and Google reviews the FAQ is candid about the limit: Yelp does not allow third-party posting, "so WALO writes you the perfect reply in seconds; you paste it. Same for Google reviews." That is the correct answer and it is unusual to see a product admit it on its FAQ.
Explain: what is covered and what is not
The follow-up a customer actually wants is the one that answers "what am I getting." Because Service Pricer quotes are structured — line items with quantities and unit prices, the warranty as its own line, the discount named — the draft can list them rather than summarize them. The homeowner sees "Smart motor + app, 14 stainless hinges, 10 premium rollers, install labor, 5-Year Parts & Labor, bundle savings 10%," which is exactly what the quote page shows when she taps the link. Two sources of truth that agree is the difference between a follow-up that closes and one that starts an argument.
The structured quote WALO drafts from, at phone width. Line items, warranty, tax and discount are fields, not prose, which is what lets a drafted follow-up stay exact.
Approve: the owner says send
Every outbound action waits. WALO's integrations page puts the rule in one line — "Sensitive actions stay approval-gated, so WALO can show the move before anything changes" — and the sample chat ends in "Nothing sent until you say send." For quotes and invoices specifically, Service Pricer's own send path is what fires, so the customer gets the same branded email with the owner's logo and the owner gets his usual blind copy. WALO is not a second mailer; it is a remote control for the one the owner already has.
Close loop: next follow-up, won or lost, review
After the send, the owner can tell WALO "remind me Thursday 9am to check on Maria," and the reminder lands in his timezone (an early version of the bot set reminders in UTC and woke owners at 2 a.m.; that was fixed in September 2026 and is in the record). When the homeowner picks a tier, Service Pricer notifies the owner, and the quote shows as Won in the Recent Quotes list; when the invoice is paid, the paid receipt and the review request go out from Service Pricer on their own, to every paid customer the same way.
The close of the loop lives in Service Pricer: the picked tier becomes an invoice, the card payment runs through Stripe into the owner's account, and the review request goes out after it is paid. Invoice #1042 and "AMH Garage Doors" are sample data.
The review request is the piece most owners skip and the piece with the best return. BrightLocal's 2026 survey has 97% of consumers reading reviews for local businesses. Service Pricer sends the request to one link the owner chooses and sends it to everyone who paid, which keeps it inside Google's rules against selective solicitation.
The crew, when a follow-up turns into a job
WALO's homepage has a section headed "No new app. Just text it," which is the part of WALO that goes beyond one assistant: "Run your whole AI crew from WhatsApp: Claude, Codex, Grok, Gemini and more. Text an agent's name and the job, or everyone for the whole team. Each one texts you when it starts and reports back when it's done, with a rollback ready. They run in the cloud, so no PC or terminal is needed."
The crew section of the WALO homepage at phone width. The named agents each run in the cloud under their own login and report back by text.
For a service owner the relevant use is not "build me a website" (though that is on the menu); it is "grok, update the hours on my site" or "claude, write the warranty FAQ for the garage page." Those are site changes, and they run through the engine the site calls Walrus Tusk — the AMH hub that gives the agents bounded tools, a dry run, a live health check, and an automatic rollback, without any agent ever holding the owner's Cloudflare keys. The Agent Board at walohq.com/board is the public feed of those jobs.
The Agent Board as captured on November 1, 2026. Note that the feed shows Failed as well as Shipped jobs; the board does not hide the misses.
Two things are worth saying about that screenshot. First, the counters read zero for the last 24 hours — the board shows the real feed, and on a quiet day it is quiet. Second, the feed shows FAILED jobs next to SHIPPED ones, with token counts. A product that publishes its own failure rate on a public page has made a choice about what kind of record it wants to keep, and NU respects it. The companion article in this batch, Cloudflare Ops MCP and the AMH Agent Harness, covers the engine under that board.
Everything else WALO brings to the same chat
Quote follow-up is one lane. The integrations page lists thirty connections across Google (Gmail, Calendar, Drive, Contacts, Search Console), Meta (WhatsApp Business API, Meta Business, Instagram, Facebook), Microsoft 365, Cloudflare, Stripe, GitHub, the major AI model keys, Supabase, Yahoo Mail, Resend, and a local Ollama option — plus WALO's own built-in lanes: SEO Pro, EZ Calorie, Song Seeker, Pet Cards, Rentals, Campaigns and the Developer CRM. The page's own headline numbers are 30 listed lanes, 27 ready now, 12 one-tap OAuth, and "0 passwords stored," with the note: "No fake connected claims. A lane shows Ready only when you have authorized it in your own account."
The integrations page at phone width. Each connection is the provider's own sign-in; the page says WALO never sees a password.
For a contractor the ones that matter next to quotes are Gmail (drafted replies to leads), Calendar (the Thursday slot), Search Console (the site's real rankings), and SEO Pro, which grades a site in seconds, checks the local name-address-phone consistency, shows who ranks above you for a keyword, and generates copy-paste fixes. SEO is a different article; the point here is that the owner who follows up on a quote from WhatsApp is in the same chat where he checks whether his garage-door page ranks for "spring repair Fremont."
WALO's SEO Pro page. Free audit, IndexNow submission, Search Console connection, rank radar and a competitor-gap check live on the same page as the quote assistant.
Under the hood, in plain English
The architecture is a chain, and an owner can understand every link without reading code.
The channel. The owner texts WALO's WhatsApp number (or uses the WALO web app, which installs to a phone like an app). Meta delivers the message to WALO's server as a signed webhook; the server verifies Meta's signature before it does anything else, so a forged message cannot trigger a job. An unsigned post to that endpoint is rejected — the founder's team tested that live in October 2026.
The tenant. WALO is multi-tenant: the server works out which business the sender belongs to, and whether the sender is an owner or a customer. Owners get the command set (quotes, drafts, reminders, agents, books); customers get the assistant that answers from the business's own services and prices. Each tenant's relay key — the secret an app like Service Pricer uses to talk to WALO — is stored only as a hash, so a database leak would not expose usable keys, and each app has its own; nothing is shared between tenants.
The brain. WALO's FAQ describes its default AI as "a fast, free large-language-model brain (Llama-class), with a fallback so it never goes dark." Owners who prefer their own model paste their own Grok, ChatGPT, Claude or Gemini key on WALO's "Your AI" screen; WALO tests the key once before saving it and uses it only for that owner. The no-fabrication rule sits on top of whichever brain is answering.
The tools. For a quote question, the tool is a callback into Service Pricer's endpoint for that account. For a Gmail question, it is the owner's own OAuth grant. For a site change, it is the Walrus Tusk hub, which exposes bounded operations (patch a page, read a file, purge a cache, submit to IndexNow) rather than a shell. The hub runs every write as a dry run first, applies only on approval, health-checks the live result, and rolls back automatically if the check fails.
The approval. Drafts come back to the owner. Sends happen on "send." Agent jobs that change anything ship through the hub's dry-run-then-verify gate. The WhatsApp 24-hour rule is enforced by WALO's own sending code: inside an open window it can send free-form; outside it, it will only send a pre-approved template, and it refuses free-form text rather than attempting it and failing silently.
The log. WALO keeps a chat log per tenant and, since late October 2026, records the result of every outbound WhatsApp send — the message ID Meta returned, any error code, and delivery callbacks — for seven days, with no message bodies or phone numbers in the receipt. The reason is a lesson the founder learned the hard way: a send that Meta "accepted" is not a send that arrived. The receipts let a missing reply be diagnosed from the record instead of guessed at.
Service Pricer's side. The quote, invoice, customer and job records live in Service Pricer's database behind row-level security; WALO reads through an authenticated endpoint and never touches the database directly. Payments go through Stripe Checkout into the contractor's own account at Stripe's published rate (2.9% plus 30 cents per domestic card transaction, per Stripe's pricing page); Service Pricer's site says it takes 0%. The paid receipt and the review request fire from Service Pricer's webhook handler, with an idempotency guard so Stripe's retries cannot double-send.
That is the whole chain: channel → tenant → brain → tools → approval → log, with Service Pricer as the system of record on the business side. No step requires the owner to hold a key or run a server.
What it costs, and what is free
WALO. The FAQ says: "The core runs on free infrastructure and the first week is free. The AI brain, SEO checks, and content tools cost you nothing to run — only advanced add-ons (like some rank data or premium voice) have a small cost." Rental Ops is the lane the site describes as paid; its page has an FAQ entry titled "Why is this one paid when the rest is free?" The site does not publish a price for the rank-data or voice add-ons on the pages reviewed here. Service Pricer's landing page calls the WALO lane "free."
Service Pricer. One plan at $49 a month list; the published launch offer is a 30-day free trial with a card on file and nothing charged on day one, then 50% off for twelve months ($24.50 a month), then $49, cancel anytime. The first 100 signups get Jubber, AMH's website assistant, included while subscribed. A trial code unlocks a 14-day trial without a card.
WhatsApp itself. Meta's pricing is per message by category, with free allowances for service conversations and entry-point windows, and customer-initiated replies inside the 24-hour window are where free-form messaging lives. Template messages outside the window are the ones that carry a per-message price. That is Meta's bill, not WALO's; an owner should read Meta's pricing page before planning a template campaign.
Card processing. Stripe's, at Stripe's published rate, into the contractor's own account.
Bring-your-own-AI. If an owner pastes his own model key into WALO's Your AI screen, that provider bills him directly; WALO's free brain costs nothing.
Honest limits and what is still being built
This section is the record of what is not finished, because a quote follow-up tool that overclaims is worse than none.
WhatsApp is in early access. The public README for the AMH hub says it plainly: "early access while Meta finishes verifying WALO's number — link your number and you'll be in as soon as it opens. Until then, everything works in the WALO app." The founder's October 2026 round-trip test showed the number live and messages arriving, but also an intermittent Meta error tied to display-name approval, with business verification still pending submission. That is Meta's gate. The web app does not have it.
Accepted is not delivered. WALO's own receipt log records that a message Meta accepted may not have reached the handset. If a reply goes missing, the receipts are the first place to look; they are owner-only and contain no bodies or numbers.
Service Pricer is the only wired live-data lookup. Other apps on the same WALO bridge can get an owner alert and a chat, but "where's my order" or "what did I quote" for a different app needs its own callback added in code. The multi-tenant data model is ready; the per-app lookup is not generic yet.
Yelp and Google reviews are paste-only. WALO drafts the reply; the owner posts it. Yelp does not allow third-party posting, and WALO's FAQ says so.
QuickBooks is built but waiting on Intuit. WALO has a QuickBooks lane where each user connects their own books and asks "books who owes me" or "books P&L last month," with every write dry-run by default. It is live as code and blocked on Intuit's developer-app approval for real connections. Until then it is "in progress," and Service Pricer itself does not sync to QuickBooks.
Agent jobs fail sometimes. The Agent Board shows FAILED badges because jobs fail — an agent runs out of quota, a site check does not pass, a handoff times out. The design is that a failed job rolls back and reports; it is not that jobs do not fail.
Proactive texting needs templates. WALO cannot text a customer who has not texted first without a Meta-approved template, because that is WhatsApp's rule. A "follow up with every quote from last week" campaign over WhatsApp is a template-approval project, not a toggle. Email campaigns do not have that constraint, and WALO's Campaigns lane exists for them.
Free brain, free limits. The default model is a free-tier hosted model with fallbacks. It is fast and good enough for drafts; it is not a frontier model, and the FAQ does not pretend it is. Owners who want a specific model bring their own key.
One company, small team. Both products are built and operated by a working garage-door contractor and a very small crew. The build record shows a product that gets patched the same day a bug is found — the 2 a.m. reminder bug, the made-up phone number, the silent email failure — which is both the appeal and the risk. There is no enterprise support desk.
The founder's own review of the pairing is in the current short article and still applies: "I love it. It makes it simple as a business owner. I couldn't ask for more!" — Austin Little, whose Austin's Affordable Garage Door is the business both products were built inside.
A 30-day playbook
Week 1 — Get the record straight. Sign up for Service Pricer's trial. Load the logo, the company name exactly as Google shows it, and the ten parts you quote most. Connect Stripe from Settings so the Pay button exists. Build a quote for a job you did last month and compare the computed total to what you charged.
Week 2 — Quote everything, follow up from the truck. Sign up for WALO (Google or WhatsApp sign-in; if WhatsApp is still early access for you, use the web app). Connect Service Pricer. Every new job gets a Service Pricer quote link, and every customer question gets a WALO-drafted reply within the hour — read it, fix a word if you need to, say send. Set a reminder in WALO for each open quote: "remind me Thursday 9am about Maria."
Week 3 — Close the loop on paper. Mark quotes won or lost as they resolve. Let the invoice go out from the picked tier, and let the paid receipt and review request run on their own. Point the review link at your Google profile. Reply to every review from the WALO draft — paste it, do not skip it.
Week 4 — Count. Quotes sent, links opened within an hour, follow-ups sent within an hour, tiers picked, invoices paid online within seven days, reviews posted. Compare to the month before you started. The two numbers that decide it are follow-up-within-an-hour and reviews-posted; if both moved, the pairing is paying for itself. If they did not, cancel Service Pricer (the site says you can) and keep WALO, which is free.
Do not do in month one: template campaigns over WhatsApp (needs Meta approval and a reason), auto-assigning techs (watch the manual flow first), or letting any agent change your website until you have read one dry-run diff and one rollback report on the Agent Board.
Frequently asked
Does WALO send messages to my customers on its own? No. Drafts come to you; sends happen on your "send." The homepage sample ends with "Nothing sent until you say send," and the integrations page says sensitive actions are approval-gated.
Where does WALO get my quote numbers? From your Service Pricer account, by calling back into Service Pricer's endpoint each time you ask. It does not keep a copy and it does not guess; a number it cannot look up is a number it will not state.
Can my customers text my WhatsApp and get answered? WALO's FAQ says yes — customers text, WALO replies 24/7 in their language from your real prices, and moves them toward booking, and you get the lead either way. The WhatsApp lane is in early access while Meta verifies WALO's number; the web app works now.
Can WALO post my review replies? It drafts them. You paste them. Yelp does not allow third-party posting and Google reviews are handled the same way.
What does WhatsApp cost? Meta prices per message by category. Replies inside the 24-hour customer-service window fall under its service-message allowances; template messages outside the window carry a per-message price. Read Meta's pricing page before planning proactive campaigns.
Can a customer pay from the chat? WALO's FAQ says yes when paired with Service Pricer: the customer gets the quote or invoice link over WhatsApp and pays from the link. The payment itself runs through Stripe into your account.
Is my data safe? Service Pricer's privacy page names its four vendors (Supabase, Cloudflare, Stripe, Resend) and says it does not sell data. WALO's integrations page says it stores no passwords and that each connection is the provider's own OAuth. Neither product is audited by a third party, and neither claims to be.
What is Walrus Tusk and do I need it? It is the engine inside WALO that lets the AI crew change sites safely — dry run, approval, health check, rollback. If you only want quote follow-up, you never touch it. If you ask an agent to edit your website, that is what runs.
Who makes these? Service Pricer LLC, operating as Artificial Mind Hive, founded by Austin Little, a Fremont, California garage-door contractor.
Where to learn more
- Service Pricer: The Contractor SaaS Built Around Quotes, Jobs, and Real Operator Pain — the full walk-through of the quote, invoice, payment and dispatch side.
- Cloudflare Ops MCP and the AMH Agent Harness — the open-source engine under the Agent Board, and why the agents never hold a key.
- The Agent Harness Pattern — the general design: bounded jobs, independent checks, receipts.
- WALO — the product; its FAQ, Integrations, SEO Pro and Agent Board pages are the primary sources for this article.
- Service Pricer — the product.
- Artificial Mind Hive — the studio; Agent Book for Jubber and the agent roster; Apiary for the mirrored edition of this piece.
Sources (the record)
- WALO — homepage (sample conversation, "Nothing sent until you say send," the WhatsApp crew section) — WALO / AMH
- WALO — FAQ (customer replies, email drafts, Yelp/Google paste-only, Service Pricer quotes and invoices, pricing, AI brain) — WALO / AMH
- WALO — Integrations (30 lanes, 27 ready, 12 OAuth, 0 passwords stored; approval-gated actions) — WALO / AMH
- WALO — Agent Board (public live feed, "powered by Walrus Tusk," dry run / health check / rollback) — WALO / AMH
- WALO — SEO Pro — WALO / AMH
- WALO — Rental Ops (the paid lane) — WALO / AMH
- Service Pricer — landing page (WALO lane, sample quote and invoice, pricing and launch offer) — Service Pricer LLC
- Service Pricer — privacy policy (vendors, card handling) — Service Pricer LLC
- AMH WT (Walrus Tusk) — public repository README (WALO + WT relationship, WhatsApp early-access note) — GitHub
- Artificial Mind Hive — studio homepage — AMH
- Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads," Harvard Business Review, March 2011 — Harvard Business Review
- Meta — WhatsApp Business Platform pricing (per-message categories, 24-hour customer service window, free allowances; updates effective Oct. 1, 2026) — Meta for Developers
- Meta — WhatsApp conversation types and customer service windows — Meta for Developers
- Twilio — WhatsApp key concepts (24-hour window, message templates) — Twilio
- Twilio — Send WhatsApp notification messages with templates — Twilio
- Google — Read & reply to reviews; request reviews with a link or QR code — Google Business Profile Help
- Google — Prohibited and restricted content for reviews (no incentives, no review gating) — Google
- Yelp — How do I respond to reviews? — Yelp Support
- BrightLocal — Local Consumer Review Survey 2026 (97% read local reviews) — BrightLocal
- FTC — Trade Regulation Rule on the Use of Consumer Reviews and Testimonials, effective Oct. 21, 2024 — Federal Register
- Stripe — Pricing (2.9% + 30¢ per successful domestic card transaction) — Stripe
- Stripe — Webhooks (event delivery and retries) — Stripe
- Jobber — Pricing — Jobber
- Housecall Pro — Pricing — Housecall Pro
- ServiceTitan — Pricing — ServiceTitan
- Intuit — QuickBooks Online API: get started (the lane WALO is waiting on) — Intuit Developer
- IETF — The OAuth 2.0 Authorization Framework, RFC 6749 (how "connect" works without a password) — RFC Editor
- Austin's Affordable Garage Door — the founder's field business — Austin's Affordable Garage Doors
Originally published on Nothing Unseen, an Artificial Mind Hive (AMH) site. AMH is owned by Austin Little. Product pictures are screenshots of the live sites; tap any picture to open the product.