--- title: "AI Builder Cohort" description: "Get one thing built that you've wanted automated, by your own technical person, with review every week. Four weeks, application-based, founding cohort." url: https://services.edgeteam.io/builder/ updated: 2026-10-07 --- # Get one thing built that you've wanted automated, by your own technical person, with review every week. | Fact | Value | | --- | --- | | Price | $1,497 (list price $1,997) | | Length | Four weeks | | Paid by | Card | | Book | [Apply by email](mailto:admin@edgeteam.io?subject=AI%20Builder%20founding%20cohort%20application) | Four weeks. Your builder scopes one build on day one, works on it in a live build session and a clinic every week, and ships a deployed system in your accounts with a README someone else could run. Application-based. Founding cohort $1,497 (list price $1,997). [Apply by email](mailto:admin@edgeteam.io?subject=AI%20Builder%20founding%20cohort%20application&body=AI%20Builder%20founding%20cohort%20application%0A%0A1.%20Name%2C%20email%2C%20company%2C%20role.%0A%0A%0A2.%20What%20do%20you%20want%20to%20build%3F%20One%20paragraph.%20Include%20the%20trigger%20(what%20starts%20it)%2C%20the%20output%20(what%20it%20produces)%2C%20and%20who%20uses%20it.%0A%0A%0A3.%20What%20problem%20does%20it%20solve%2C%20and%20how%20is%20that%20work%20done%20today%3F%0A%0A%0A4.%20Do%20you%20have%20access%20to%20the%20system%20or%20data%20it%20needs%3F%20(yes%20%2F%20partly%20%2F%20not%20yet)%0A%0A%0A5.%20Which%20describes%20you%20best%3A%20I%20write%20code%20%2F%20I%20build%20in%20no-code%20tools%20%2F%20I%20read%20code%20and%20can%20modify%20it%20%2F%20none%20of%20these.%0A%0A%0A6.%20What%20have%20you%20built%20with%20AI%20so%20far%2C%20if%20anything%3F%20Links%20welcome.%0A%0A%0A7.%20Which%20tools%20do%20you%20plan%20to%20use%3F%20(Claude%20Code%2C%20an%20agent%20SDK%2C%20Make%20or%20n8n%2C%20other)%0A%0A%0A8.%20Can%20you%20attend%20Wednesday%2011%3A00%20and%20Friday%2012%3A00%20Central%20for%20four%20weeks%3F%0A%0A%0A9.%20Are%20you%20an%20EdgeCore%20member%2C%20an%20EdgeCore%20Pro%20member%2C%20or%20attending%20through%20an%20EdgeCorporate%20program%3F%20(affects%20seat%20type%2C%20not%20acceptance)%0A%0A%0A10.%20Anything%20else%20Dan%20should%20know%20before%20reviewing%3F%0A%0A) ## Who it's for You have a technical person, or you are one: comfortable in a terminal or a no-code automation tool, or able to read and modify code. You have a real problem from your business or a client's business, access to the system or data it involves, and a specific thing you want automated or an agent you want running. **Not for:** people who want a repeatable workflow inside a chat tool. That's [Zero to Hero](https://services.edgeteam.io/zero-to-hero/), and we'll say so in the application reply. ## What you get at the end - **One build, bounded and deployed.** A single trigger, a single output, a single user, running somewhere other than your builder's laptop, in your accounts. Week one exists to cut the project down to that, because the most common failure in builder programs is a project that's three projects. - **A README someone else could run it from.** It comes with a written list of the ways the build fails and what was done about each. Week three is about failure: bad input, tool errors, refusals, hallucinated fields, cost. - **A builder who has shipped once, with Dan reviewing.** Every Wednesday at 11:00 Central, Dan builds the week's step on a reference project from a blank state, on camera, including the decisions he abandons and the things that break. Every Friday at noon, your builder shows their build running or failing, and Dan reads the code or the flow with them and names the one change that matters most. ## What it asks of you Two hours a week of your builder's time for four weeks, plus build time between sessions. Access to the system or data the build touches, sorted before week one. A business-tier account on the AI platform they'll use. ## The four weeks | Week | Wednesday build | Friday clinic | By Friday your builder has | | --- | --- | --- | --- | | 1 | Scope and stand up | Scope review | A scope sentence, an environment, a first successful call | | 2 | The core path | Debugging | The right output on three real inputs | | 3 | Survive contact: evals, failures, guardrails, logging, review points, cost | Failure clinic | A failure list with fixes, ten real inputs run | | 4 | Ship: deploy, README, handoff, what to monitor | Demo day | A deployed build and a certificate | ## What it costs $1,497 (list price $1,997) a seat, by card, after the application is accepted. The founding cohort is priced below the list price because it's the first run and we'll ask your builder for feedback every week. EdgeCore members and EdgeCorporate participants attend through their programs. ## What it is not Every week is your builder's build, so there's no curriculum to consume. Claude Code and the Claude API are the default path, and builders on Make, n8n, or another agent framework are welcome. Business-tier accounts are required, and the terms say so, because client data doesn't belong in personal accounts. ## Where this comes from This cohort hasn't run yet, which is why the first one is application-only and priced as a founding run. The outcome it exists to produce we've watched happen once, slowly: an operations lead at a real estate company with no developer background who, over four months of weekly review, moved her project from a no-code tool to a real application, deploys through GitHub, runs the tests through Claude, and now ships every week. Four weeks is that loop, compressed. ## Apply Ten questions, about fifteen minutes. The button opens an email to admin@edgeteam.io with the questions already in it: answer them and send. You can fill it in for your builder or have them do it. Dan reads every application and replies within three business days with one of three answers: you're in, not this run and here's the specific thing to sort out first, or this isn't the right program and here's the one that is. [Apply by email](mailto:admin@edgeteam.io?subject=AI%20Builder%20founding%20cohort%20application&body=AI%20Builder%20founding%20cohort%20application%0A%0A1.%20Name%2C%20email%2C%20company%2C%20role.%0A%0A%0A2.%20What%20do%20you%20want%20to%20build%3F%20One%20paragraph.%20Include%20the%20trigger%20(what%20starts%20it)%2C%20the%20output%20(what%20it%20produces)%2C%20and%20who%20uses%20it.%0A%0A%0A3.%20What%20problem%20does%20it%20solve%2C%20and%20how%20is%20that%20work%20done%20today%3F%0A%0A%0A4.%20Do%20you%20have%20access%20to%20the%20system%20or%20data%20it%20needs%3F%20(yes%20%2F%20partly%20%2F%20not%20yet)%0A%0A%0A5.%20Which%20describes%20you%20best%3A%20I%20write%20code%20%2F%20I%20build%20in%20no-code%20tools%20%2F%20I%20read%20code%20and%20can%20modify%20it%20%2F%20none%20of%20these.%0A%0A%0A6.%20What%20have%20you%20built%20with%20AI%20so%20far%2C%20if%20anything%3F%20Links%20welcome.%0A%0A%0A7.%20Which%20tools%20do%20you%20plan%20to%20use%3F%20(Claude%20Code%2C%20an%20agent%20SDK%2C%20Make%20or%20n8n%2C%20other)%0A%0A%0A8.%20Can%20you%20attend%20Wednesday%2011%3A00%20and%20Friday%2012%3A00%20Central%20for%20four%20weeks%3F%0A%0A%0A9.%20Are%20you%20an%20EdgeCore%20member%2C%20an%20EdgeCore%20Pro%20member%2C%20or%20attending%20through%20an%20EdgeCorporate%20program%3F%20(affects%20seat%20type%2C%20not%20acceptance)%0A%0A%0A10.%20Anything%20else%20Dan%20should%20know%20before%20reviewing%3F%0A%0A) ## The ten application questions 1. Name, email, company, role. 2. What do you want to build? One paragraph. Include the trigger (what starts it), the output (what it produces), and who uses it. 3. What problem does it solve, and how is that work done today? 4. Do you have access to the system or data it needs? (yes / partly / not yet) 5. Which describes you best: I write code / I build in no-code tools / I read code and can modify it / none of these. 6. What have you built with AI so far, if anything? Links welcome. 7. Which tools do you plan to use? (Claude Code, an agent SDK, Make or n8n, other) 8. Can you attend Wednesday 11:00 and Friday 12:00 Central for four weeks? 9. Are you an EdgeCore member, an EdgeCore Pro member, or attending through an EdgeCorporate program? (affects seat type, not acceptance) 10. Anything else Dan should know before reviewing?