Pricing, AI, and performance notes
How Pengo is actually built, priced, and billed. Written by the team, not marketing copy.
-
Shipping a mobile agent app that matches the web inbox
Search, attachments, assignment, password reset, push deep links, and status labels - how the Pengo Flutter app stays in sync with the dashboard agents already use.
#mobile #product
-
How we built agent analytics without melting Postgres
A walkthrough of Pengo's analytics pipeline: server-side aggregation, agent productivity tables, Recharts on the dashboard, and CSV export - without loading entire message histories into the browser.
#engineering #analytics
-
Designing a chat state machine that agents actually understand
Why we replaced ad-hoc status flags with a explicit pending → open → resolved lifecycle, and what that means for routing, analytics, and the mobile app.
#engineering #product
-
Keeping the chat widget under 5KB gzipped
Most chat widgets ship 100-300KB of JavaScript on every page load. Here's how Pengo's facade pattern keeps the initial payload under 5KB - and how to verify it yourself.
#engineering #performance
-
Why we stopped billing per resolution
Per-resolution AI billing sounded fair on paper. In practice it created disputes, unpredictable invoices, and a product story we did not want to sell. Here is what we changed and why.
#ai #pricing #product
-
Why Pengo doesn't charge per seat
Per-seat pricing punishes the exact behavior you want from a support team: adding more people. Here's why we built Pengo differently.
#pricing #product