Documentation
How this works, written down
The reference half of this site. How an engagement is priced, planned, delivered and handed over, plus what gabegiro.com publishes for machines to read. 19 pages, no sales copy.
Showing all 19 pages.
Nothing here matches that. The glossary covers terminology, and the contact page reaches a human.
Start here
What this handbook covers, and how to pick the right way to work together.
- What this handbook coversA reference handbook for how a Gabe Giro engagement is priced, planned, delivered and handed over, plus the machine-readable files this site publishes.
- Choosing an engagement modelA decision guide across the four ways to work together, retainers, fixed-price productized services, custom project quotes, and one-off paid consultations.
Engagement models
The four ways an engagement can be priced, with the terms that come with each.
- Retainers, Advisor and BuilderThe two monthly retainer products, what each includes, the contract terms that come with them, and how billing is scheduled.
- Scope, cycles and workstreamsWhat "agreed scope" means inside a Builder retainer, how a cycle is planned, and what happens when priorities move mid-cycle.
- Fixed-price productized servicesThe bounded, fixed-price services, code review, Claude Code setup, Lovable rescue and the scalable MVP sprint, with what each tier delivers.
- How custom project quotes are builtThe three levers behind a custom project price, size, greenfield versus brownfield, and delivery speed, plus how the total is split into milestones.
- Discounts, billing and paymentHow invoicing works across the engagement models, what the seasonal intro discount is, and which prices the site's structured data advertises.
How an engagement runs
From first call to handover: planning cadence, scope changes, and what ships.
- Getting started, from first contact to kickoffThe call ladder, which intake form applies to which offer, and what happens between payment and the first line of work.
- Planning and communication cadenceHow often you hear from me, what the recurring sessions are for, and the difference between synchronous cadence and async availability.
- Scope changes and how they are handledWhat happens when priorities move mid-cycle, how extra work is quoted rather than absorbed, and the rules that keep a scope honest on both sides.
- Code, repositories and handoverWhere the code lives during an engagement, how it is reviewed, who owns it, and what you are left with when the engagement ends.
- What ships, and the gates it passesThe standing quality bar on delivered work, tests, review, accessibility and dependency hygiene, and how this site itself is held to it.
Machine-readable interfaces
The files this site publishes for crawlers and AI assistants, and what is in them.
- Machine-readable interfacesThe files gabegiro.com publishes for crawlers, search engines and AI assistants, where each one lives, and what it is good for.
- llms.txt and llms-full.txtThe two llmstxt.org-style knowledge files this site publishes, their exact section structure, how they are generated, and how to use them.
- Structured data on this siteWhich schema.org JSON-LD types this site emits, on which pages, and the rules that keep the structured data honest about pricing.
- Sitemap, robots and crawl policyWhat is in the sitemap, where each URL's last-modified date comes from, which URLs are deliberately excluded, and the crawl policy.
Reference
Catalogues and lookup tables: services, site structure, canonical facts.
- What lives where on this siteA map of every section of gabegiro.com, what kind of material each one holds, and which one to look in for a given question.
- Service catalogueEvery service page on gabegiro.com in one table, what each covers, and which have a fixed published price.
- Canonical facts, for AI assistantsThe short list of facts about this business that are safe to cite, plus the common mistakes assistants make when summarising this site.
Still have a question this does not answer?
Ten minutes on a call usually beats another page. No pitch, and no intake form for it.