Work
Seven projects, each described in depth: three public products we built and operate, and four outreach platforms built for a software client under confidentiality. Every case shows the problem, the architecture, what was delivered and the stack, with dated facts and no invented metrics.
Seven projects: three public products that we designed, built and operate ourselves, and four data and outreach platforms built for one software client under confidentiality. Together they cover web platforms, public APIs and MCP servers, data pipelines, CRM hand-offs and compliant email outreach.
The three named products:
Four confidential platforms, built for one software client on a shared outreach core: startup discovery and outreach, agency partner sourcing, affiliate reactivation and affiliate recruitment. Each instance runs isolated, with its own database, dashboard and sending identity, while opt-outs recorded by one are honored by all.
A wall of logos tells you little about how a team builds. A case that shows the data model, the build gates that stop a bad deploy, how scores are computed and how the data pipeline runs tells a CTO or a business owner far more. So each case covers the challenge, the solution, the functionality, the integrations and the stack, and states only facts we can verify in the code or on the live site, with a date.
The confidential cases have no screenshots. They show the pipeline stages and the engineering choices instead: idempotent daily runs, deduplication, suppression lists shared across instances, read-only integrations with the client’s systems and role-based dashboards.
If you want to see how these patterns apply to your own project, the services overview lists what we build, and get a quote starts the conversation.
FAQ
They were built for a client whose outreach strategy is part of its competitive advantage. We therefore publish no client name, domains, data sources or volumes. What we can show is the pipeline, the engineering decisions and the generic stack, which is what matters when you judge how we build.
InboxRatio has been live since August 2026, PingMyUsers and WABA Index since September 2026. Of the four outreach platforms, two are in daily production use and two are built and tested. Each case page states its status and the date it was checked.
For our own products such figures would be self-reported and young, and for client work they belong to the client. We publish what can be checked instead: what is live and since when, and counts taken from the code and data, such as the number of profiled services or API tools, with the date they were counted.
The three products run on Next.js, React, TypeScript, Tailwind CSS and MDX, with data kept in git and compiled at build, hosted on Vercel. The outreach platforms run on Python with FastAPI, SQLAlchemy and PostgreSQL, deployed with Docker Compose behind Nginx. Two products also publish a REST API with an OpenAPI document and a read-only MCP server.
No. InboxRatio, PingMyUsers and WABA Index are products we built and operate ourselves. They let us show complete systems, from data model and scoring engine to content workflow and SEO, without client confidentiality limits. The four outreach platforms are client work.
A Swiss technology company in Lugano.