jared hebb ~ %

Terms

Terms of Use

Last updated: October 26, 2026

This site (jaredhebb.com) is run by Jared Hebb. By using it you agree to what is on this page. If you do not agree, stop using the site.

What this site is

A personal site. It holds writing about work in progress, a list of things built, guides about Claude Code, and a set of free generators that turn answers to a few questions into a config file you can paste somewhere. It is not a product with a support contract, and nothing here is professional advice. Two things on it are paid and have their own sections below: the Role Build service and website design projects.

The free tools

The generators on this site run in your browser. Nothing you type into one is sent to a server or stored. What they produce is a starting point meant to be read and edited, not something to paste into a live system without looking at it. You are responsible for what you do with the output, including checking it against the current documentation for whatever tool it configures. Those tools change, and a file that was correct when it was generated can stop being correct later.

Role Build

Role Build is a paid service for one office seat in your business: a paid diagnostic that maps the seat, a fixed-price build that puts its repeat work on systems in your own accounts, and a monthly fee to keep those systems running. This section is a plain summary of how it works so you can read it before booking a call. It is not the contract. The contract is a signed agreement with your seat, your price and your workflows named in it, and where the two ever disagree, the signed agreement is what governs.

The fit call is free, thirty minutes, and there is nothing to sign before it. If a diagnostic is not worth doing for your seat, I say so on the call and that is the end of it.

For the diagnostic you give me a separate, read-only account on each tool the seat uses, limited to its settings and configuration. I see how the tool is set up and where your data lives, never the data itself. Where a tool cannot separate the two, you choose how we handle it: a wider read-only account, showing me the settings on a call, or I work from the tool's documentation.

The diagnostic is $2,500, paid before it starts, and takes about two weeks from the day the payment clears. The clock moves if the person in the seat is out or access is slow, and you are told the new readout date the same day. It ends in a written report, walked through with you in a readout meeting: every task in the seat with its hours, what the seat costs you, the systems a build has to reach, every task ranked, the seats the build covers, and the monthly tier I recommend. If another seat in your business does the same kind of repeat work, the report names it and its rough hours a week. If you sign the build agreement within ninety days after the readout, the full $2,500 comes off the first build payment. The credit is never paid out in money and does not apply to the monthly fee. If you cancel before the kickoff meeting, or I cannot start, the $2,500 comes back in full. Once the kickoff has happened, the diagnostic fee is not refundable.

The build is a flat $20,000 for each seat, and the diagnostic report says which seats and tasks are in scope. Half is due when you sign and half on the go-live date, and the price does not change unless we both sign a change to it. Work starts on the later of your first payment clearing and me having the access the build needs, and the schedule pauses while I am waiting on you for a decision or a login.

If you already know the seat you want off your plate, you can pay the whole build up front instead of the diagnostic first. You pay $20,000 a seat before anything starts and sign a one-page prepayment agreement. The diagnostic runs the same way, except that its credit and its early refund do not apply, because the build is already paid, and the build follows the readout with nothing more to pay. Paying up front adds one thing: once the build starts, I map a second seat in the same detail as the first, every task with its hours, what it costs you and what a build would cover. For any seat the diagnostic finds not worth building, what you paid for that seat comes back except $2,500 for its diagnostic. The same holds for any seat you decide not to build, if you tell me in writing within thirty days of the readout and before the build starts. If I cannot start the build, the same $2,500 a seat is all I keep, and if I cannot finish the diagnostic, everything comes back. A delay on your side, such as access that never arrives, is not a reason for a refund: the payment stays with the build, which starts when you are ready. If twelve months pass after the readout without the build starting and without that written notice, the build is no longer owed and nothing is refunded.

Each workflow is described in the agreement by what sets it off, what it does, where the result lands and what counts as done. A workflow that does not do what the agreement says is not delivered yet, and it gets worked on until it does, at no extra cost and with no time limit on the fixing. You can raise that at any point until the included support window ends. Changing your mind about what a working workflow should do is new work, not a defect.

Every build goes live within thirty days of the day work starts. Before you sign, you name one or two people on your side who can make decisions and answer my questions within twenty-four hours, weekends included. We meet once a week until go-live, and after each meeting you get a short written summary: what got done, what is next, and anything I am waiting on from you. If anything moves the date, I tell you in writing promptly, with the reason and the new date. The build ends in a live demo, with everyone in the room, of every workflow running in your accounts.

Cancel before work starts and every build payment comes back, except on a build paid up front, where the paragraph on paying up front says what comes back. If illness or something outside either of our control stops the work for more than fourteen days, you can cancel and get back everything you paid for the build, or on a build paid up front, everything except $2,500 a seat. Otherwise you can still cancel once work has started, in writing: the first half is not refunded, the second half is not owed, or comes back if you paid it up front, and anything already live stays in your accounts.

The first sixty days after go-live are close support, included in the build price. The monthly starts the day after that, so you never pay for both at once. It is labor only, and there are three tiers.

On every tier, repairs to anything already live, and the monitoring that catches the break, are unlimited. However short the punch list gets, I spend time on your systems every month, checking how each workflow ran, improving what can run better, and suggesting what goes on the list next. Unfinished work carries into the next month, and unused time does not. You can change tiers in writing, and the change takes effect on the next billing date.

The monthly has no minimum term and no cancellation fee. Either of us can end it at any time, for any reason, with thirty days' written notice. Email counts. Billing stays monthly in advance as normal, and the work and the billing continue through the thirty days and stop there. If a billing date falls inside the notice period, that charge covers only the days left until the notice period ends, prorated by the day. Say you give notice on the 1st and your billing date is the 15th: the charge on the 15th covers the 15th to the end of the thirty days, not a full month. Nothing is billed after the notice period ends. Apart from that proration, a period already billed is not refunded.

Two things run the other way and belong here rather than buried in a contract. The monthly fee holds for twelve months from the day the monthly starts, and after that it can change with thirty days' written notice, which you can decline by cancelling with no fee, and the new price never applies during those thirty days of notice. And if an invoice goes unpaid for fifteen days, the work can be paused after telling you first, meaning no new work and no monitoring. Nothing is ever switched off over an unpaid invoice; what is live stays live.

You own and pay for every account the build runs on: the AI provider, the automation platform, and any other software. Each one is opened in your name and paid by you directly to the vendor on your own card, usage charges included. My fees never include software costs, and I never pay or advance them for you. No new paid account is opened without your written approval. The agreement lists each account with a good-faith estimate of its monthly cost, and it is an estimate rather than a promise, because usage charges move with volume.

If you started Role Build under the earlier offer, a one-time setup and $750 a month, you keep that offer. The $750 holds for twelve months from your start date, and you are not moved onto the terms above without thirty days' written notice.

You keep everything either way, and it keeps running. It was built in your accounts on your own logins, so nothing is switched off and nothing is taken back, and within seven days of the work ending you get a written record of what is live and what each workflow depends on. What ends is the management, meaning no new work and nobody watching it when something upstream changes. That last part is the one worth reading twice, because a workflow nobody is monitoring eventually breaks quietly.

Work does not start until access does: the build schedule does not begin until I have what the build needs. The form it takes is your call, whatever you are comfortable granting. My own preference, stated for every tool involved, is a separate account made for this and limited to what the work needs: an invited seat, a limited key, or an OAuth connection through the tool's own permission screen. I will not ask for the password to your main account, on any tool, as a condition of doing this work, and I would tell you not to hand it over if you offered. If a tool genuinely has no scoped option, the credential goes in a shared password manager entry, never in an email or a text, and it is deleted the day the work ends.

Your data stays yours and is used only to build and run what the agreement describes. It is never sold, your customers are never mailed, and none of it trains anything. I use AI tools, including Anthropic's Claude, to build and in some cases to run what gets built; where a workflow itself calls an AI service, the agreement names it, because that is a place your data goes. Copies held outside your own accounts are deleted within thirty days of the work ending, or handed back sooner if you ask.

What is not promised: that a workflow will never fail, that a tool somebody else runs will keep working the way it did on the day we built, or that any of this produces a particular business result. Nobody has been promised revenue, a hire avoided, or a number. The remedies above are the remedies. As with everything else here, this is one person, and the most you can recover for any problem with the service is what you paid for it in the preceding twelve months.

Website design projects

Website design is quoted one project at a time. Each client gets a written agreement for their project, linked in the email that carries the payment link and named on the checkout page. Checking the box to accept these terms when you pay for a website project also accepts that agreement. Where the two disagree, the project agreement governs.

No warranty

This site and the free tools on it are provided free of charge, "as is," with no warranty of any kind, express or implied, including accuracy, fitness for a particular purpose, and non-infringement. Use of anything here is at your own risk. Pages can be wrong, out of date, or offline. Role Build has its own warranty and liability wording in its section above, and a website project has its own in its project agreement. Those govern them.

Who owns what

The writing, page design, and code on this site belong to Jared Hebb. Quoting a short passage with a link back is fine. Republishing a page or a set of pages somewhere else is not, without asking first. Output you generate with the free tools is yours to use however you want, with no credit needed. The hooks, skills and standards checkers published in the public hooks and skills repository are MIT licensed and carry no restriction at all, wherever you found them.

Product and company names on this site belong to their owners. "Claude" and "Claude Code" are trademarks of Anthropic, PBC. This site is not affiliated with or endorsed by Anthropic.

Acceptable use

Do not try to disrupt the site, scrape it at abusive volume, or work around how it normally operates. Do not use the email signup to submit an address that is not yours.

Links to other sites

Some pages link to sites and products run by other people, and a few of those links are affiliate links that pay a commission if you buy something. Those sites have their own terms and their own privacy practices, and this site is not responsible for what they do.

Changes to these terms

These terms may be updated as the site changes. The date at the top says when this page last changed. Continuing to use the site after an update means you accept the revised version. For Role Build the rule is stricter: once an agreement is signed, nothing on this page changes it. That agreement is only changed in writing, by both of us. The same holds for a website project agreement once it is accepted.

Contact

Questions about these terms: jared@jaredhebb.com.

This page is a plain description of the terms this site is used under, not legal advice, and has not been reviewed by a lawyer. See also the privacy policy.