Ongoing Partnership

Hedge Development Plan

How we keep building features for Hedge โ€” without the overhead of traditional development.

How It Works

You describe what you want. Our AI-assisted system builds it, tests it, and deploys it. You review the result and tell us if it's right.

๐Ÿ“
You File a Request
Plain English, no code
โ†’
โšก
System Builds It
Code, test, deploy
โ†’
๐Ÿ‘€
You Review
On the live site
โ†’
โœ…
Ship It
Close the ticket
๐Ÿ’ก

If it needs changes? Just comment on the ticket with what's off. The system picks up your feedback and iterates. No need to re-explain โ€” just say what needs to change.

1

Submit a Request

Create a ticket on your board. Can be as simple as "The onboarding should ask about certifications" or as detailed as you want. Screenshots and examples are always helpful.

2

We Build and Deploy

The system reads your request, writes the code, runs checks, and deploys to hedgesystems.org. You get a notification with what changed and how to test it.

3

You Review

Check it on the live site. If it's right, close the ticket. If it needs tweaks, comment and we'll iterate. If it's wrong, say so โ€” redirecting is fine.

What Can You Request?

โ— Great Fit โ€” Fast Turnaround

  • โœ“ UI changes, layouts, colors
  • โœ“ Bug fixes
  • โœ“ New data or fields on pages
  • โœ“ Assessment questions & courses
  • โœ“ Admin panel features
  • โœ“ Scraper updates & data cleanup

โ— Possible โ€” Needs Discussion

  • ~ Entirely new features
  • ~ Third-party integrations (Stripe, etc.)
  • ~ Mobile app changes

โ— Outside Scope

  • โ€” Full design overhauls
  • โ€” Native hardware features
  • โ€” Writing hundreds of questions

Sharing What You Have in Mind

The more context you share, the closer the first version is to what you want. You don't need to write specs โ€” just show us what you're thinking.

๐ŸŽจ

Lovable / Design Prototypes

Paste the preview URL from Lovable, Figma, or any prototyping tool. We'll match the layout, colors, and interactions.

๐Ÿ“ธ

Screenshots & Mockups

Drop screenshots directly into your ticket. Annotate them, circle things, draw arrows โ€” whatever helps explain it.

๐Ÿ”—

Reference Apps & Links

"Make it work like this page on [other app]" is a perfectly valid request. Link to anything that shows what you mean.

๐Ÿ“„

Docs & Spreadsheets

Google Docs, Sheets, PDFs โ€” link them in the ticket. Great for assessment content, business data, or workflow descriptions.

๐Ÿ’ฌ

The best tickets look like: A sentence or two describing what you want + a screenshot, Lovable link, or example. That's it. No wireframes or technical specs needed โ€” just show, don't tell.

EXAMPLE TICKET:

Title:  Add team export to company page

Body:   I want a button on the Company โ†’ Info tab that downloads
        a CSV of all team members. Should include name, email,
        role, and credentials earned.

        Here's a Lovable prototype of what I'm thinking:
        https://lovable.dev/projects/abc123

        And here's how another app does it:
        [screenshot attached]

Priority: Normal

What You Have Access To

๐Ÿ“‹

Request Board

File feature requests, bug reports, and ideas. Track progress on each one.

๐ŸŒ

hedgesystems.org

The live app. All changes deploy here. This is what your users see.

โš™๏ธ

Admin Panel

Manage assessments, courses, and businesses at hedgesystems.org/admin

๐Ÿ”

Contractor Directory

Browse 3,000+ scraped contractors at hedge-directory.pages.dev

๐Ÿ’ป

Source Code

Full codebase on GitHub (Hedge-Systems/hedge). Yours to keep, forever.

๐Ÿ“–

Documentation

HANDOFF.md covers everything a future developer would need.

How the System Works

A look at the full loop โ€” from your request to the deployed feature.

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚                     YOUR REQUEST                                โ”‚
โ”‚        "Add an export button to the team page"                โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                           โ”‚
                           โ–ผ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚  AI DEVELOPMENT SYSTEM                                        โ”‚
โ”‚                                                                 โ”‚
โ”‚  1. Reads the full codebase + your request                      โ”‚
โ”‚  2. Writes the code changes                                     โ”‚
โ”‚  3. Runs type checks & automated tests                          โ”‚
โ”‚  4. Verifies pages load correctly (browser tests)                โ”‚
โ”‚  5. Deploys to Cloudflare                                       โ”‚
โ”‚  6. Comments on your ticket with results                        โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                           โ”‚
                           โ–ผ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ hedgesystems โ”‚    โ”‚  Admin Panel โ”‚    โ”‚ Contractor Directory โ”‚
โ”‚  .org         โ”‚    โ”‚  /admin      โ”‚    โ”‚ hedge-directory      โ”‚
โ”‚              โ”‚    โ”‚              โ”‚    โ”‚ .pages.dev          โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
      โ”‚                     โ”‚                       โ”‚
      โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                           โ”‚
                           โ–ผ
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚                   YOU REVIEW & RESPOND                          โ”‚
โ”‚                                                                 โ”‚
โ”‚     โœ“ Looks good โ†’ Close ticket                                โ”‚
โ”‚     ~ Needs tweaks โ†’ Comment โ†’ System iterates                  โ”‚
โ”‚     โœ— Not right โ†’ Redirect โ†’ System rebuilds                    โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

How Fast Things Get Built

Same Day

Bug fixes, text changes, layout tweaks

2โ€“3 Days

New page features, admin tools, data views

~1 Week

Major new features, integrations

Build vs. Explore

Not every request is "build this exact thing." Sometimes you want to try an idea, test a direction, or see what's possible before committing. We handle both.

๐Ÿ”จ

Build Track

Ships to production

You know what you want. We build it, test it, and deploy it. The standard flow.

  • โœ“  Clear outcome
  • โœ“  Deploys to live site
  • โœ“  Same-day to 3 days
  • โœ“  You review on hedgesystems.org
"Add an export button to the team page"
๐Ÿงช

Explore Track

Experimental โ€” you decide if it ships

You have a vague idea or want to try something. We build a prototype, you look at it, then decide: ship it, change direction, or scrap it.

  • ~  Direction might change
  • ~  Preview before going live
  • ~  3โ€“7 days for a prototype
  • ~  No risk โ€” doesn't touch production
"What if we had a client-facing dashboard showing their team's progress?"
                    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
                    โ”‚   YOUR REQUEST    โ”‚
                    โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                             โ”‚
                    โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ดโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
                    โ”‚ Clear or vague?  โ”‚
                    โ””โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”˜
                        โ”‚          โ”‚
                   Clear โ”‚          โ”‚ Vague / Experimental
                        โ”‚          โ”‚
                        โ–ผ          โ–ผ
              โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”  โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
              โ”‚ BUILD TRACK โ”‚  โ”‚ EXPLORE TRACK โ”‚
              โ”‚             โ”‚  โ”‚              โ”‚
              โ”‚ Implement   โ”‚  โ”‚ Prototype    โ”‚
              โ”‚ Test        โ”‚  โ”‚ Preview      โ”‚
              โ”‚ Deploy      โ”‚  โ”‚ Get feedback โ”‚
              โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”˜  โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”ฌโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                     โ”‚                โ”‚
                     โ–ผ                โ–ผ
              โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”  โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
              โ”‚ LIVE ON SITE โ”‚  โ”‚ YOU DECIDE   โ”‚
              โ”‚ You review  โ”‚  โ”‚              โ”‚
              โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜  โ”‚ โ†’ Ship it    โ”‚
                              โ”‚ โ†’ Change it  โ”‚
                              โ”‚ โ†’ Scrap it   โ”‚
                              โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
๐Ÿงช

Explorations are low-risk. They're built on a separate branch โ€” nothing touches the live site until you say "ship it." This is a great way to try ideas like new page layouts, Lovable designs, or features you're not sure about yet.

How We'll Communicate About Experiments

1

We share the approach first

Before building anything experimental, we'll comment on the ticket with what we're thinking โ€” the direction, roughly how long it'll take, and any tradeoffs. You approve, redirect, or say "not now."

2

You get a preview

Once the prototype is ready, we share a preview link โ€” a version of the site with the experimental feature included. You test it without affecting any real users.

3

You make the call

Ship it โ€” we deploy to production. Tweak it โ€” we iterate based on your feedback. Scrap it โ€” no harm done, nothing was ever live. All three are fine.

What This Costs You

$0
No hourly rates. No retainers. No per-feature fees.
Your only costs are the infrastructure you're already running โ€” all on free tiers.
Service Cost Status
Cloudflare (hosting, database, storage) Free tier Well within limits
Clerk (authentication) Free up to 10K users 4 users
Chuck AI (Anthropic) ~$0.01 / conversation Pay as you go
hedgesystems.org domain ~$15 / year GoDaddy renewal
๐Ÿ“ˆ

If Hedge grows past the free tiers? Costs scale gradually โ€” there are no cliff edges. You'd need thousands of active users before hitting paid tiers.

What We Get Out of It

Full transparency: we're building AI development tools at Threshold Labs. Hedge is a real production app with real users and real feature requests โ€” exactly the kind of environment we need to test and refine our tools.

Your feature requests become our test cases. When something works well for Hedge, we know it works well in general.

๐Ÿ”’

We're not experimenting on your app. The features you get are production-quality. The process of building them is what we're refining.

Getting Started

1

We set up your request board

A simple place to file tickets. We'll do a 15-minute walkthrough so you're comfortable with it.

2

Start filing requests

Anything you've been wanting โ€” bug fixes, feature ideas, content needs. Don't hold back.

3

We respond on each ticket

Either with a deployed change, a question, or a note about timeline.

4

Weekly update (optional)

A quick async summary of what shipped and what's coming up. No meetings required unless you want one.

Common Questions

What if something breaks?

The system runs automated checks before deploying. If something does break, file a ticket marked "urgent" and it gets priority treatment.

Can we still hire a developer later?

Absolutely. The full codebase is in your GitHub organization with complete documentation. This arrangement doesn't create lock-in.

How long does this arrangement last?

As long as it's working for both sides. If you outgrow this and want to hire a full-time developer, the codebase will be in excellent shape. If we decide to wind down, we'll give you notice and make sure everything is documented.

Who do we contact if we have questions?

Ryan at Threshold Labs. Same person, same communication channels you're used to.