Home Work
Case studies — or, honestly,
what we've built.
Here's the truthful version: we're a young studio, and we don't have client logos or five-year testimonials yet. What we do have is production software we designed, wrote and run ourselves — on exactly the stack we'd build for you. That's the proof on this page.
The honest version
No client logos. Real software instead.
The same standard as our About page: fake reviews — zero, invented metrics — zero. If we haven't done it, we won't claim it.
A lot of agencies open with a wall of borrowed logos and rounded-up numbers. We'd rather show you the software we live with daily than the clients we don't have yet. Every product below is something we scoped, engineered and now operate ourselves — with the bugs, the uptime and the design decisions all on us. When we recommend a pipeline, a mobile stack or a verification step, it's because ours has been running on it around the clock, not because it read well in a deck. Judge the engineering. That's what you'd be hiring.
Built & running
The software we operate.
Five build stories. Each one live, each one ours, each one on the stack we sell.
LeadProwl — a lead-data platform
The problem. Sales teams burn hours stitching together scrapers, enrichment tools and verification services that don't talk to each other. What we built. LeadProwl is a single lead-data platform and marketplace: scraping and data collection, decision-maker enrichment, email verification and outreach — as connected pipeline stages rather than a pile of subscriptions. The engineering. Python and FastAPI over PostgreSQL, with Celery-backed queues and schedulers doing the heavy, around-the-clock work so a slow enrichment step never blocks the rest. Honest status. Live and in active development — the platform we push new pipeline work into first.
Stack — Python · FastAPI · Postgres · Celery queues
Status — live, in active development
NoMailBounce — email verification
The problem. Sending to dead or risky addresses quietly wrecks deliverability and sender reputation. What we built. NoMailBounce is a standalone email-verification service with a fast front end and a clean API — check an address, get an honest verdict. The engineering. A React/Vite front end over a Node API, built to be called both directly and as a service. It's also the verification engine embedded inside LeadProwl, so the same code that powers the product does the verification step in our lead pipelines. Honest status. Live, and doing double duty as our own infrastructure.
Stack — React/Vite front end · Node API
Doubles as — LeadProwl's verification engine
Unbuilt Lab — startup-idea research
The problem. Founders guess at what to build instead of reading real demand signals. What we built. Unbuilt Lab discovers startup ideas end to end: it scrapes signals across the web, clusters them with NLP, generates candidate ideas with AI, then scores each one across multiple dimensions so the promising ones surface. The engineering. Python and Flask over PostgreSQL with Celery workers running the scraping and processing pipeline, plus a mobile app built in React Native / Expo — one codebase across iOS and Android. This is the AI-plus-data pattern behind our automation and research work, running for real. Honest status. Live, with the mobile app in active development.
Stack — Python/Flask · Postgres · Celery · Expo/React Native
Pipeline — scrape → cluster → generate → score
The template library — front-end craft, live
The problem. "We do great websites" means nothing without something clickable. What we built. Nineteen complete, animated marketing websites — every one hand-coded here, no themes and no page builders. The engineering. Hand-written HTML, CSS and JavaScript with self-hosted fonts, designed light and dark modes, and load times that keep both Google and visitors happy. Honest status. All nineteen are live and clickable right now, and any of them can be re-forged around a brand in days.
Stack — hand-written HTML/CSS/JS · self-hosted fonts
Proof — 19 live, all animated
This site & its chatbot — the portfolio piece you're on
The problem. An agency site should demonstrate the work, not just describe it. What we built. The site you're reading is hand-coded top to bottom — no page builder anywhere — and in the corner is a self-hosted RAG chatbot, grounded in our own content so it answers from fact and hands off when it should. The engineering. Hand-written front end plus a self-hosted LLM/retrieval stack (Dify) we run ourselves rather than renting a black box. Honest status. Live — this page, and the assistant in the corner of it, are both the proof.
Stack — hand-written front end · self-hosted LLM/RAG (Dify)
Proof — you're using it
What this means for you
You get the same engineering — and you own it.
The person who built and runs these products is the one who builds yours. The scars are already paid for — your project starts on patterns proven in software we operate daily.
We ship the smallest honest slice that proves value, so you learn from real users before over-building — the same way we grew each product above.
Hand-written code, documentation and credentials handed over. No page builders, no black-box subscriptions, no lock-in — the code is yours to inspect and keep.
Want the detail on how each capability maps to a build? The services page breaks it down, and our write-up on mobile app case studies and what actually makes them succeed is the same thinking applied to product work.