Kape Tools

Two systems, and exactly how they were built

Long-form accounts of real builds: the decisions, the trade-offs, the things that broke, and the numbers that can be checked. Written by the person who built them. No invented metrics, no client logos, and no testimonials.

Case study

Building a marketing website from scratch with Claude Code

A long-form marketing site for a professional-services practice, hand-built as static HTML, CSS and vanilla JavaScript with no framework and no build step.

Hand-written static site / 100 commits / zero npm dependencies

Hand-written HTML5CSS with 32 custom propertiesVanilla JavaScriptGSAP 3.12.5ScrollTriggerLenis 1.1.13

Read the build

Case study

Building a content and automation system that one person can run

Four months of operations engineering inside somebody else's marketing platform, ending in a deliberate decision not to build the software that was asked for.

Operations tooling, GoHighLevel automation, and a deliberate no-code recommendation

React 19ViteTypeScriptTailwind CSS v4React Router 7Supabase

Read the build

How these are written

Every figure on these pages can be re-derived from a repository, a live page or a build log. Where something was not measured, the page says so instead of estimating. Client names, brand identities and proprietary frameworks are left out on purpose, so the engineering can be described honestly without publishing somebody else's business.

They are written by Kenneth Villar, who builds these systems at BrewedOps in the Philippines. If you want to see the output rather than read about it, the free guides and the freelancer tax calculator were built the same way, and what Kape Tools costs is public.