Farai Kepekepe

Systems Builder — Subcontractor Brief
farai@kepekepe.com
kepekepe.dev
LinkedIn
What I Build

I build operational systems that sit between raw data and business decisions. The work ranges from workflow automations in n8n, to advanced formula engines in Google Sheets, to full-stack web applications with API layers and CI/CD. I operate at whatever layer of the stack the problem requires — a formula in a cell, a webhook integration, or a containerised .NET API. Every deliverable ships with documentation and is built for handover, not dependency.

Technical Stack
CategoryTools & Technologies
Workflow Automationn8n, JavaScript, REST APIs, webhooks
Data ProcessingGoogle Sheets (ARRAYFORMULA, QUERY, LET, XLOOKUP, FILTER), Apps Script
BackendASP.NET Core 8, C#, SQL Server, REST API development
FrontendReact, Vite, Tailwind CSS
InfrastructureDocker, Docker Compose, GitHub Actions, Plesk, Caddy, Oracle Cloud
What I've Built — Proof of Work

AI Evaluation & Proposal Pipeline

n8n → Gmail trigger → dual-model LLM (primary + Groq fallback) → Google Sheets → Telegram

Ingests job postings via email, evaluates fit using a dual-model LLM architecture with automatic failover, generates proposals, routes by priority, and sends Telegram alerts. Production system with idempotent logging and structured error handling.

Operational Liquidity Control System (OLCS)

Google Sheets → 5-layer architecture: Ingestion → Normalisation → Memory → Control Engine → Dashboard

Converts MYOB AR/AP accounting exports into forward liquidity projections with payment terms modelling, monthly forecasting, and deterministic control logic. Two production variants delivered for the same client group. YouTube walkthrough available.

Idempotent Stripe Ledger Automation

n8n → Stripe API → Airtable (state ledger) → Google Sheets → Google Drive → SMTP

Automates receipt processing with an external state ledger ensuring idempotent invoice handling — no duplicate processing regardless of trigger frequency. Demonstrates engineering maturity in production automation design.

How to Engage
Availability
Up to 12 hours/day, flexible scheduling
Timezone
UTC+2 — significant overlap with UK and US East
Engagement Model
Day rate or project rate. You bill the client, I build the system.
Communication
Email, Slack, or whatever your team uses
Deliverables Include
Working system + documentation + handover