What changed on this site

A new service page for the credit retainer: a pre-paid monthly plan where each fix or feature costs a known number of credits, agreed before any work starts. Unused credits roll over.

Every fixed-price service and both retainers now cost a quarter of what they did. The scope of each offer is unchanged; the pricing page and each service page show the new figures.

Every page now points at the same email, info@gabegiro.com, and the contact page shows it in plain sight instead of hiding it behind a form.

QR codes on Zoom backgrounds and printed material that point at my LinkedIn now pass through a short /go/ link on this site, which records the visit before forwarding. Calls booked from a Zoom background carry their own source too, so I can tell which offline channel actually brings people in.

Pages without their own preview image now share with a proper default card on LinkedIn, Slack and other link previews, instead of pointing at an image that did not exist.

Four posts that had been sitting on the blog as coming-soon teasers got their full bodies and went live: GitHub Actions Is the Weakest Link, Your AI Skill Catalog Has a Token Tax, Zero Billable Hours: The Case for One Writer and Launch Your Task Agents in Plan Mode, Not Auto.

Form submissions, booking clicks and CTA clicks were being lost because the browser navigated away before analytics could send them. Those events are now handed over to the next page and sent from there, so the funnel is measurable end to end.

A new /docs section: 19 reference pages on how engagements are priced, planned, delivered and handed over, plus what this site publishes for crawlers and AI assistants (llms.txt, sitemap, structured data). Prices on those pages are read from the same source as the pricing page, so they cannot go stale.

Every JSON-LD block on the site was deepened so search engines and AI assistants get a complete description of each page, with a build-time check that fails if any block is too thin.

A walkthrough of how I keep a client's Kotlin codebase legible to Claude Code: what goes into CLAUDE.md, what re-orientation costs without it, and where to start.

A field guide to the ways n8n workflows fail in production and how to catch each one before a client does.

Blog posts can now be merged ahead of time and go live on their release date, so publishing no longer depends on someone pressing a button that day.

Both the light and dark themes were reworked to meet WCAG 2.2 AAA contrast, checked automatically on every build. A new /accessibility page states the target, the known gaps and how to report a problem.

Every booking button on the site now goes through one component, opens the right calendar slot for its context, and opens external calendars in a new tab. Paid checkouts land on a new thank-you page.

The /compare page was rebuilt as a plain checkmark matrix comparing a senior solo engineer with a freelancer, an agency, a full-time hire and no-code platforms, including where I am not the right fit.

Two new reference pages: a glossary of the terms used across the site, and a security page describing how I handle client code, data and access, without certification badges I do not hold.

A single /pricing page listing every service tier, with the same prices published as machine-readable offers for search engines and AI assistants.

A downloadable six-page PDF on taking an engineering team from "we use Claude" to measurably shipping more, listed in a new Guides gallery on the portfolio page.

The homepage, about page and audience pages were rewritten around what I do now: AI features and adoption, mobile apps, and full-stack delivery. A new /ai-engineer landing page goes with it.

A site-wide summer discount for July through September, shown consistently on every service page and at checkout.

Older posts gained purpose-built figures (before and after comparisons, scorecards, pull quotes) and a short-version summary at the top of every post.

A new /portfolio page brings demos, tools and case studies together, with showcase pages for projects that are not public yet, starting with Voyage and Command Center.

How I give my AI coding agent a council of documentation-backed experts to consult before it plans.

Upcoming posts can appear on the blog as teasers with a subscribe option, so readers can ask to be told when they land.

An account of moving an app off Lovable Cloud without losing a day of uptime.

The homepage started routing visitors to a landing page written for their situation, instead of one page trying to speak to everyone.

Case studies for AR Art Projector, FYX, Papaya and Preglife joined the existing ones.

A new /about page with the background behind the work.

Every service now lives at one canonical /services// address, with the old URLs redirecting there.

The site moved off WordPress to a new build, with service pages, case studies and the existing blog posts carried over.