Services
Website buildCustom-coded, fast, no page buildersApplication buildInternal tools, portals, multi-tenant productsAI agentsScoped permissions, full activity log, kill switchInnovation consultingI diagnose one problem and prototype the fixCollege coachingCourse strategy, portfolio, internships, interviewsCompany interviewI come to you, interview your team, and post itMore
ProductsHow we workAsk AIAboutHow engagements work
Every project runs on the same four terms. They are on this page rather than in a contract you read once at signing, because the worst time to learn how an engagement works is halfway through one.
Your site is designed, written, and hosted on my infrastructure — source code in my GitHub, deployment on my Vercel account. That means one person is responsible when something breaks at eleven at night, and there is no shared-access tangle to unpick before a fix can ship. You get a site that is looked after, not a pile of credentials you are now in charge of.
Your domain name is yours, registered to you. Everything you bring — your copy, photographs, logo, and brand — stays yours and leaves with you. The source code and the repository stay with GrizzlyBare, and client access to the code, the repo, or the hosting is not part of the engagement at any stage, including after the final payment clears. You are buying a working site that I keep working, not a codebase to take in-house.
The full project fee is due before the site is published. Launch day is the last step, not the invoice date — so there is never a question of a live site with an open balance, and never a conversation about switching one off. You see the finished work on a preview link before you pay, so nothing about it is a surprise.
Once the site is live, any further change — new copy, a new page, a fix, an addition — is billed at $70 an hour. Nothing starts until you have said yes to the work and to the estimate, so the number on the invoice is one you agreed to beforehand. Small edits usually land well under an hour; I will tell you when something is going to run longer before I begin.
In order
Four steps, in this sequence, every time.
A call about what you are trying to do rather than what you want built. Half of it is usually me talking you out of something. You get a scope and a fixed price for the build.
Built on my infrastructure. You see it on a private preview link as it comes together, and you say what needs changing while it is still cheap to change.
You sign off on the finished site on the preview link. The full project fee is due at that point — before it is published, not after.
I publish it and it is my job to keep it up. Anything new after that — a page, a fix, a change of copy — is $70 an hour, quoted and agreed before I start.
Still deciding what to ask for? Put the question to the site — it answers from what is written here.
Questions about any of it?
If something here doesn't suit how you want to work, it is better we both know on the first call.