CRM · live site
teamgoldllc.de ↗
Bilingual EN/DE marketing site with correct hreflang, four JSON-LD schema types, non-blocking font loading.
01 The shelf
Book a callBuilt, shipped and operated by one person. Every number on this page is a measurement, not a claim.
Routine work runs unattended: a library of reusable agent skills, and a scored policy that decides which model and how much reasoning each task gets. One gate sits in front of every action with a price on it.
The one everything else runs on
A cold-calling CRM with a browser softphone, an outbound AI voice agent, and the scoring that decides who gets called. Scroll: it comes apart.
Sample rows, scored and tiered by the real thresholds. No customer data appears on this page.
The first scoring version multiplied need by budget by reachability. Mathematically reasonable, and it pushed almost the whole dataset onto a handful of duplicate scores. Drag the sliders and watch both formulas at once.
Measured on the real dataset: 9,400 of 59,725 leads landed on the identical score 35. The bars are all 9,261 combinations of the three inputs in steps of 5, in 20 bins.
An always-on pipeline that finds local businesses, checks they still exist, and reads their own websites for signal. Two scrapers cross-verify each other before anything is scored.
Both lanes read the same 11 rows, the same two writes land mid-scan, and only one lane gets it right. Press play. The general-purpose fix is on GitHub as postgrest-keyset-page.
OFFSET n LIMIT 30 duplicates · 0 skippedWHERE id < last_seen LIMIT 30 duplicates · 0 skippedRow 11 gets inserted, then row 6 gets deleted, both mid-scan. Exactly the timing that broke this in production.
Measured on the real dataset: a 20-minute scan with 43 concurrent inserts produced exactly 20 duplicate reads under offset paging.
The watchdog restarts the scraper only after confirming real CPU activity over a window. Checking whether the process id still exists proves nothing.
"Never measured" and "measured, and it is zero" look identical in a spreadsheet and mean opposite things to a scoring model.
A dependency-free pre-commit hook that stops API keys reaching a commit, written after five live credentials sat in a repo for months. Building a labelled corpus of 61 cases surfaced three bugs, all false negatives: the failure mode that looks exactly like success.
The real patterns, ported to JavaScript. Four lines are pre-filled and each produces a different verdict: a catch, a placeholder, the prose that caused a real false positive, and an explicit opt-out.
Runs entirely in this browser. Nothing you type into the scanner leaves the page. View the repository.
Two of the twenty-five are public and running right now. Both are screenshots of the live thing, not mockups.
teamgoldllc.deBilingual EN and DE with correct hreflang, four JSON-LD schema types, non-blocking font loading.
FahmA side project, phone-first: one HTML file, no build step, 500+ Quranic words with word-by-word breakdowns.
A missed call becomes a text to the caller, a logged lead, and an alert to the owner, in under 60 seconds. Built for a two-person crew who are on a roof when the phone rings.
A Windows box and an Ubuntu ARM instance. SSH password authentication off entirely, keys only. Debug ports bind to loopback. Secrets live in the OS keystore, enforced by the hook above and again in CI.
Smaller in scope than the six above. Each one a real, independently working subsystem, not a stub.
CRM · live site
Bilingual EN/DE marketing site with correct hreflang, four JSON-LD schema types, non-blocking font loading.
CRM · Data
Two independent scoring layers: geometric-mean need/budget/reachability, and a separate ICP-fit score with its own confidence metric.
Data · AI
Merges signals from several observation sources into one profile per contact; reports confidence separately from freshness.
Data · AI
Parses a business's own website for hiring activity, ad-spend evidence, tech stack and multi-location signals, from data already fetched.
Data · AI
Five more signals out of one page load already being made, with 0 additional network calls, plus public licence-registry matching that needs two independent fields to confirm a name.
AI · CRM
Splits recorded calls into separate customer and agent channels before transcription; measurably better than letting the model guess the speaker.
AI · CRM
LLM-generated rep feedback gated behind human approve, edit or reject, plus a blind grading mode so review is not biased by the AI's verdict.
CRM
Coordinates an email warm-up ramp, a queued LinkedIn channel, and a layer that labels measured numbers apart from self-reported ones.
CRM · Data
Test-cohort system with independent locks keeping test leads out of production automation, plus a self-releasing batch mechanism.
AI · Security
Model Context Protocol servers exposing read-only business data and a security-testing toolkit, scope-gated off by default.
AI
Telegram approval bridge letting a long-running agent pause and ask before any money, access or direction decision.
AI
Scored, versioned policy deciding which model and how much reasoning effort a task gets, across eight escalation signals.
Data · AI
A separate monitor checking whether the checker is still alive, built after a daemon died silently for three days.
Security
Wraps nmap, nikto, sqlmap and whatweb behind a scope gate that refuses anything outside localhost and private ranges unless deliberately unlocked.
CRM
A legal calling-hours check kept strictly separate from reachability scoring. The two answer different questions.
CRM · Data
A rep pool rings first, with a server-enforced lock forcing a voicemail fallback regardless of any dashboard toggle.
AI · CRM
Rotates which market segment the calling operation focuses on, driven by measured rep success rates.
AI · Personal
RSS-based channel monitoring with no paid API, feeding a pipeline that extracts business and engineering lessons.
Personal · public repo
Single-file, build-free web app for Quranic Arabic: 500+ words, word-by-word breakdowns, custom vocabulary import.
Personal
A chess engine, a crypto-trading backtester, and classic learn-to-code exercises. Kept private, and the actual starting point.
Built by directing coding agents deliberately: writing the specification, setting the guardrails, verifying the result. No degree; what replaced it was building real systems, operating them, and fixing what broke. No customer data, phone numbers or business metrics appear anywhere on this page or in the linked repositories.
Who builds this
How he works, and where he came from. The stack that shipped it all is right below.
I build fast by directing AI coding agents deliberately — writing the specification, setting the guardrails, and verifying the result — rather than typing every line by hand. That's a real, current skill: the systems above aren't demos, they run a real business every day, and treating "the agent said it's done" as a claim to verify rather than a fact was the single habit that mattered most in building them.
No customer data, phone numbers, or business metrics appear anywhere on this page or in the linked repositories; numbers are rounded, not exact.
I didn't come to this through a computer science degree. The short version:
No university degree — what replaced it was building real systems, operating them, and fixing what broke.
What actually shipped the systems above — not an aspirational list.
Tap any item for what it means in plain words — no jargon.
Pick one of the five, or type your own.