Custom App Build Terms
Version 1.0, effective August 22, 2026
These terms cover the Custom App Build included with Agent Ops Club membership. Where they differ from the Member License Agreement, these terms govern the application built for you.
1. What you get
One custom web application, designed and built by Mark Fulton, delivered as a private repository you own and a live deployment running in your own accounts.
Scope is comparable to a product in the club library: one core job done properly, rather than a platform. A first version that works and can be sold beats a large specification that never ships, and scope is agreed with you on a call before any work starts.
2. Who can claim, and how often
- Every member with an active membership may claim one build. One per member, for the lifetime of the membership.
- I accept two builds per calendar month, first come first serve, in the order claims arrive.
- If the current month is full, your claim keeps its position in the queue and moves into the next available opening. Nothing expires and nothing needs reclaiming.
- The live counter on the club site shows how many openings remain in the current month.
3. What I build
Included:
- A focused web application: accounts, authentication, and role based access
- Stripe subscriptions or one time payments
- A working dashboard, plus the admin screens needed to operate it
- An agent or automation layer, including scheduled routines
- Integration with one or two third party APIs you already have accounts for
- Deployment to your own domain, in your own Vercel and Supabase accounts
Not included:
- Native iOS or Android applications
- Anything holding funds, custody, or regulated financial activity
- Products requiring HIPAA, SOC 2, or similar certified compliance
- Blockchain, token, or crypto custody products
- Ongoing feature development after the delivery and revision round
- Content production, data entry, or migration of large existing datasets
If your idea sits outside this list, say so when you claim. Some of it I can still do, and I would rather tell you before you queue than after.
4. Ownership
You own the delivered application outright and exclusively. That means the source code, the intellectual property, the brand, and all revenue it ever earns.
I retain no license to it, take no equity, and take no revenue share. It does not enter the club library, it is never resold, and it is never shown to another member as a product. Generic engineering patterns are not exclusive to anyone, and reusing a common pattern in later work does not touch your ownership of what was built for you.
5. Timeline
- Scope call within one week of your claim being accepted.
- Build typically ships two to four weeks after the scope call. If a queue or a holiday changes that, you get a date, not silence.
- One revision round, requested within fourteen days of delivery, covering corrections and adjustments to what we agreed. New features are a new project.
6. What I need from you
- The idea, the audience, and how it earns.
- Accounts for anything third party: domain, Vercel, Supabase, Stripe, and any API the build needs. The app lives in your accounts from day one, so nothing has to be handed over later.
- Responses to scope questions within a few days. Two weeks of silence returns your claim to the queue so the opening goes to another member, and you may claim again whenever you are ready.
- Any third party costs. There are no charges from me, but domains, API usage, and paid service tiers are yours.
7. The optional launch push
If you want it, I will introduce your launch to my network, currently 325,000+ Facebook community members and 14,000+ on LinkedIn.
This is entirely optional. It is not a condition of the build, declining it changes nothing, and I take no revenue share either way. I will not promote anything I consider misleading or harmful, and I will say so rather than quietly not doing it.
8. Membership
Your membership must be active when you claim and while the build is in progress. Once delivered, the application is yours permanently, whatever happens to your membership afterwards.
9. Fair use
This is a genuine bonus, not an agency retainer in disguise. One build per member keeps it available to everyone. I may decline a request that falls outside section 3, that I am not the right person to build, or that would require work I am not willing to put my name on. If I decline, I will tell you why, and your claim is returned so you can propose something else.
10. No warranty
The application is provided as is. You are responsible for operating, securing, and maintaining it after delivery, and the Masterclass exists to make that straightforward. I am not liable for damages arising from your use of it, to the maximum extent permitted by law.
