Own business system · case study
Team Gold CRM
Lead management, browser calling and follow-up in one workflow. The case study explains the architecture and selected code excerpts.
Video · recorded locally with synthetic data.
Developer · open to technical partnerships
Custom software.
Built around your workflow.
I’m Atakan, a developer from Germany. I build web applications and connect the tools a business already uses.
Selected work.
Videos, screenshots and diagrams alongside each project. Each project page explains the structure, decisions and limits.
Guided demo · sample appointments
Voice receptionist
A receptionist flow for service businesses: capture the enquiry, confirm details and offer sample appointments. The browser demo uses fixed replies.
1:37 minutes · scripted call with a fictional business. No real appointment booking.
Developer tool
git-secret-scan
A pre-commit hook and GitHub Action detect supported key and token formats. The documentation explains the checks, benchmark and limits.
Published schematic example of a blocked commit.
Learning application · public app
Fahm
Review, hear, write and read Arabic vocabulary in context. A small web application with locally stored learning progress.
Actual capture of the public site, 2 Nov 2026.
Research · experimental
AutoLM
A small language model built from scratch: tokenizer, transformer, training and evaluation of generated n8n workflow skeletons. Results and limits are documented.
Structure diagram derived from inspected sources; not a running model demo.
Workflow · infrastructure
Multi-machine agent sync
Shared working context and Git backups across macOS, Linux and Windows. The case study explains file responsibilities and the documented sync workflow.
Published workflow diagram; not a live machine-status display.
Automation with human checkpoints.
An automation design combining reusable agent skills, model routing and approval checkpoints for actions involving money, access or direction.
- 20+purpose-built agent skills
- 8escalation signals in the routing policy
- 2processes: worker and watchdog
The one everything else runs on
The screen is the easy part.
The CRM I built for my own business brings lead management, browser calling and outreach into one workflow. The diagram below shows its main layers.
The public case study documents the private CRM with selected code excerpts and synthetic screenshots. Counts below describe the reviewed source snapshot. Read the CRM case study ↗
- 01What the operator sees. One trade at a time, with the measured runway of each lead pool.
- 02What decides who gets called. Two scoring layers, geometric mean, an explainable tier per lead.
- 03What can stop it. Spend cap, call window, and a kill switch no single toggle overrides.
- 41dashboard pages
- 159server API routes
- 3access roles
Scoring layer
lead · hvac · reachable612S
lead · roofer · mailbox388A
lead · plumber · no site271C
Sample rows, scored and tiered by the real thresholds. No customer data appears on this page.
Guardrail layer
spend capcall windowkill switchrow-level security
One multiplication destroyed the ranking.
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.
An earlier scoring version produced too many tied scores. The chart compares both formulas across all 9,261 input combinations in steps of 5.
Old, raw product0tier
New, geometric mean0tier
Every possible lead, both formulas
score 01000
It has to be right at 3am, not just at noon.
A lead-data pipeline built to find local businesses, check their websites and compare signals from two independent scrapers before scoring.
- 2independent scrapers, cross-verified
- 30+business signals per lead
Live · offset paging against a table that keeps changing
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 skipped
WHERE id < last_seen LIMIT 30 duplicates · 0 skipped
Row 11 gets inserted, then row 6 gets deleted, both mid-scan. Exactly the timing that broke this in production.
Engineering lesson: cursor pagination avoids shifting offset windows when rows are inserted or deleted during a scan.
A dead browser looks exactly like a healthy one.
The watchdog restarts the scraper only after confirming real CPU activity over a window. Checking whether the process id still exists proves nothing.
A null is not a zero.
"Never measured" and "measured, and it is zero" look identical in a spreadsheet and mean opposite things to a scoring model.
I measured my own security tool. It was at 80%.
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.
- 98tests, 98% coverage
- 11CI jobs across 3 operating systems
- 80 → 100%recall, after measuring it. Precision 91.4 → 100%
Live · paste something and watch
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.
Things other people actually open.
Public web projects and a guided phone demo. The screenshots show earlier versions of the applications; the links open the current sites.
teamgoldllc.deBilingual EN and DE with correct hreflang, four JSON-LD schema types, non-blocking font loading.
Portrait, same buildMobile is the first target, not a pass at the end.
FahmA side project, phone-first: one HTML file, no build step, 500+ Quranic words with word-by-word breakdowns.
Phone receptionist · guided demo
A receptionist flow for service businesses: capture the enquiry, confirm contact details and offer sample appointment slots. Try it in English or German.
The browser demo uses prerecorded replies and sample slots. It does not make a real booking. The case study includes the call flow, audio examples and video pipeline.
Infrastructure and shared working context.
The multi-machine-agent-sync case study documents shared working context and Git backups across macOS, Linux and Windows. Read the case study ↗
More projects and engineering work.
A mix of standalone tools and components built within larger systems. Public work samples are linked where available.
CRM · live site
teamgoldllc.de ↗
Bilingual EN/DE marketing site with correct hreflang, four JSON-LD schema types, non-blocking font loading.
CRM · Data
Lead Scoring & ICP Engine
Two independent scoring layers: geometric-mean need/budget/reachability, and a separate ICP-fit score with its own confidence metric.
Data · AI
Multi-Source Data Fusion
Merges signals from several observation sources into one profile per contact; reports confidence separately from freshness.
Data · AI
Hiring-Signal Detection
Parses a business's own website for hiring activity, ad-spend evidence, tech stack and multi-location signals, from data already fetched.
Data · AI
Multi-Source Lead Enrichment
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
Two-Channel Call Audio
Splits recorded calls into separate customer and agent channels before transcription; measurably better than letting the model guess the speaker.
AI · CRM
AI Call Review & Coaching
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
Multi-Channel Outreach
Coordinates an email warm-up ramp, a queued LinkedIn channel, and a layer that labels measured numbers apart from self-reported ones.
CRM · Data
Controlled Experiment Framework
Test-cohort system with independent locks keeping test leads out of production automation, plus a self-releasing batch mechanism.
AI · Security
Custom MCP Tooling
Model Context Protocol servers exposing read-only business data and a security-testing toolkit, scope-gated off by default.
AI
Human-in-the-Loop Control
Telegram approval bridge letting a long-running agent pause and ask before any money, access or direction decision.
AI
Model / Effort Routing Policy
Scored, versioned policy deciding which model and how much reasoning effort a task gets, across eight escalation signals.
Data · AI
Self-Healing Task Watchdog
A separate monitor checking whether the checker is still alive, built after a daemon died silently for three days.
Security
Authorized Testing Toolkit
Wraps nmap, nikto, sqlmap and whatweb behind a scope gate that refuses anything outside localhost and private ranges unless deliberately unlocked.
CRM
Compliance Call Windowing
A legal calling-hours check kept strictly separate from reachability scoring. The two answer different questions.
CRM · Data
Inbound Routing with a Hard Fallback
A rep pool rings first, with a server-enforced lock forcing a voicemail fallback regardless of any dashboard toggle.
AI · CRM
Weekly Niche-Focus Controller
Rotates which market segment the calling operation focuses on, driven by measured rep success rates.
AI · Personal
YouTube Research Pipeline
RSS-based channel monitoring with no paid API, feeding a pipeline that extracts business and engineering lessons.
Personal · public repo
Fahm, Arabic vocabulary
Single-file, build-free web app for Quranic Arabic: 500+ words, word-by-word breakdowns, custom vocabulary import.
Personal
Early projects
A chess engine, a crypto-trading backtester, and classic learn-to-code exercises. Kept private, and the actual starting point.
Public examples omit private customer records and credentials. The CRM case study uses synthetic demonstration data.
Who builds this
Built by one person. Here is who.
How he works, and where he came from. The stack that shipped it all is right below.
How I work
Public examples omit private customer records and credentials. The CRM case study uses synthetic demonstration data.
Background
I didn't come to this through a computer science degree. The short version:
- ~19–21Ran online businesses — e-commerce, affiliate marketing, a YouTube channel. Learned how to get someone's attention and turn it into a customer, long before I could write a line of code.
- ~20Started learning to code, at first alongside the business work.
- 22Moved to Egypt and shifted focus fully to software.
- 22–23Freelance client work, then building my own acquisition infrastructure — cold calling, AI voice calling, email and outreach — for Team Gold, the business behind most of the systems on this page.
- NowBuilding custom software and developing technical partnerships through Team Gold.
No university degree — what replaced it was building real systems, operating them, and fixing what broke.
Skills & stack
What actually shipped the systems above — not an aspirational list.
Tap any item for what it means in plain words — no jargon.
Languages
Application & Data
AI & Agents
Voice & Messaging
Infra & Ops
Let’s talk about your project.
I’m open to technical partnerships and custom development projects. We can work through the scope together and agree on responsibilities and delivery.
Pick one of the five, or type your own.