This is not a “discount code.” It is a first-cohort trade.
If you run a plumbing shop in Frisco, an HVAC crew in Arlington, a roofing outfit in Quezon City, or a B2B service firm that lives on booked jobs, you have probably seen “founding partner” language before. Usually it means: pay less, get a vague badge, and somehow end up on a homepage carousel whether the work was good or not.
That is not what we are doing.
AridLogic’s Founding Partner Program is a small first cohort — five spots in the Sept–Dec 2026 window — for service businesses willing to help us publish the first honest case studies. In return you get founder-led delivery, Founding Partner economics on eligible packages, and priority support right after launch. The terms are written into the SOW before kickoff, not renegotiated at invoice time.
This article is a fit check. Read it the way you would screen a subcontractor: clear scope, clear ask, clear outs.
What “Founding Partner” actually includes
Here is the offer in operator language.
You get
- Founder-led delivery. AJ Rapales scopes, builds, and QA’s the project. You are not sold by one person and handed to a rotating bench you never met.
- Founding Partner economics. Up to 25% off the listed project fee on Micro, Entry, Core, or Growth — or a scoped add-on instead of a cash discount (extra automation workflow, extended QA, additional landing page). Documented in the SOW.
- Founding Partner status on the case study when we publish — a signal you helped stand the studio up, not a generic testimonial slot.
- Priority post-launch support for the first 30 days after go-live on what we shipped.
What is not discounted
Premium custom engagements stay at full scope and full price. We would rather say no than water down a build to chase a “founding” label.
You give
- A marketing release signed at SOW start (name, logo, quotes, metrics we may publish later — with your approval rights).
- Case study participation ~30 days post-launch when there is at least one measurable outcome (leads, conversion, hours saved, or an agreed proxy).
- One video testimonial (5–10 minutes) or two written quotes you approve before anything goes live.
- Logo permission on file — never used without the signed release.
- Optional but expected: up to one reference call per quarter for 12 months, scheduled with notice.
If that trade feels fair, keep reading. If it feels like a trap, stop here — you are not the buyer for this cohort.
A 10-minute fit check (yes / no)
Run these out loud with whoever signs checks.
You are likely a fit if most of these are true
- You run a home-service or B2B service business where the website’s job is booked estimates and jobs — not a brochure.
- You are shopping Micro, Entry, Core, or Growth, not trying to force Premium custom scope into Entry pricing.
- You already feel the leak: missed calls, slow follow-up, form friction, CRM that does not match the site.
- A decision-maker can join a structured interview about a month after launch.
- You are comfortable being an early public reference when real outcomes exist — not before.
- You care more about a working revenue stack (site + capture + CRM + automation) than the lowest line item on a quote sheet.
You should skip this cohort if any of these are true
- You need a logo wall or case study before work ships. We will not invent proof.
- You cannot sign a marketing release or approve published metrics.
- You want Premium-level custom work at Entry pricing.
- You are outside service businesses and need enterprise procurement theater we do not run.
- You only want a prettier homepage with the same broken follow-up behind it.
Honest outs matter. A bad Founding Partner match wastes your calendar and our five slots.
DFW and Manila: same skeleton, different skin
The program terms do not change by metro. The day-to-day does.
In DFW, owners often compare us to an agency quote that is mostly design hours, plus a separate CRM person, plus “we’ll talk automation later.” Founding Partner is for shops that want those pieces wired as one stack — and who are fine saying on a case study, six weeks later, what actually moved (callback speed, booked estimates, no-show rate).
In Manila, many operators already live in Messenger, Viber, and Facebook inquiries. The fit question is similar: will you let us measure and publish what improved after launch (with your redactions), or do you need quiet forever? If publicity is a hard no, apply for a normal engagement later — do not burn a Founding Partner seat.
Either metro: if your team cannot protect calendar windows you promise online, fix that before you buy a faster website. Speed without capacity just creates angrier customers.
What the engagement looks like (no mystery phases)
Before kickoff
- Discovery and fit check (audit or contact)
- SOW with scope, price, and Founding Partner economics
- Marketing release signed with the SOW
Delivery
- Build + automation per package
- Pre-launch QA on your site (we run a fixed checklist — not a vibe check)
- Launch with analytics and CRM wiring verified
After launch (proof window)
- Around day 30: case study interview if outcomes exist
- Draft case study + testimonial sent for your written approval
- Publish only after sign-off — we retire or edit on your written request within 14 business days
That last part is non-negotiable for us. “Founding” does not mean “we post whatever we want.”
How this ties to the rest of the revenue stack
Founding Partner is not a separate product. It is early access economics on the same stack we preach in Resources: conversion-grade site, clean capture, CRM that actually gets the lead, and automations that recover missed calls and slow follow-up.
If article A (missed call → booked job) felt uncomfortably familiar, you already know the operating problem. The fit question now is commercial: do you want to be in the first five documented builds, on founder calendar, with a structured proof trade — or do you want to wait for standard capacity after the cohort closes?
Neither answer is wrong. Only the mismatch is expensive.
Closing
Five spots. Sept–Dec 2026. Up to 25% off or a scoped add-on on Micro–Growth. Founder-led delivery. A release signed up front. A case study only when there is something real to say — and only after you approve it.
If that reads like a fair trade for your shop in DFW or Manila, start with the program page and a free audit so we are looking at your actual site, not a hypothetical. If it does not, keep using the Resources library and engage later on standard terms. We would rather keep the cohort small than fill it with bad fits.