Our Journey Building an MCP Server for Encatch
Building an MCP for Encatch started with the wrong question. Here's how we decided what AI should do, where human control stays, and what we're watching now that it's live.
Notes from Encatch
Notes, lessons, and experiments from our journey building Encatch.
Latest writing
Showing 10 of 14 articles
Building an MCP for Encatch started with the wrong question. Here's how we decided what AI should do, where human control stays, and what we're watching now that it's live.
Cookie banners force a bad trade-off between compliance and product insights. Cookieless Mode decouples Encatch's feedback SDK from tracking — nil-sentinel headers, daily-rotating server IDs, and zero-friction manual forms without waiting for consent.
Embedded AI is often limited and locked to the platform. Analyse with AI lets you export Encatch feedback data with a ready-made prompt into ChatGPT, Claude, Gemini, or any AI you already use.
Your dev queue is full, your feedback idea is on hold. Again. This guide shows PMs how to collect high-quality in-app feedback independently, no dev ticket, no form-builder headache. Set up a triggered micro-survey in under 30 minutes. Real benchmarks included.
Most PMs run feedback in bursts and wonder why it doesn't stick. Here's a realistic 90-day calendar, when to survey, who to target, and exactly what to ask, built for PMs running solo with a 30-minute window, not a research team.
Most early-stage SaaS teams discover user friction way too late, after churn already shows up in the numbers. Here's how 3 teams missed obvious friction signals hiding inside their own product, and what a 14-day feedback window could have changed for all three. If you build, you need to read this.
You shipped. Users came. Then… silence. No feedback loop at launch doesn't just mean missing data, it means shipping blind for months. Here's the real cost, and why most PMs only figure it out after they've already lost those first users.
You sent the survey, got 200 responses, opened the spreadsheet once. Sound familiar? The survey tool market is built to collect data, not to give you actual signal. Here's what's really broken, why CAPTCHA at $199/mo is just one symptom, and what a feedback system that actually works looks like.
NPS tells you what already went wrong, not what's about to. See why PMs and founders are ditching it and which real-time signals actually prevent churn.
You ran the survey, you got the responses. Then nothing happened. If your feedback is collecting dust in a spreadsheet or dying in a Slack thread, this $0 audit tells you exactly where the system broke, and what to fix before running another survey.