Customers message you on WhatsApp or email, and conversations never reach the CRM
We build chat into your portal or site. History is stored in your own database and synced to your CRM, so the account manager sees the whole conversation in one place.
Chat and live collaboration that update instantly, no page refresh
We build apps where messages, edits and statuses appear for every user at once. We start with a pilot tied to a measurable KPI, and you see the price upfront.
Quote and schedule after your brief
Who it's for
- Products where customers and account managers chat inside a portal
- Teams that need shared editing of documents, tables or boards
- Platforms with live statuses: orders, delivery, bidding, dashboards
- Founders building a SaaS who need a working first release
Problems we solve
Two people edit the same document and overwrite each other
We use CRDTs (a method for merging simultaneous edits without conflicts), typically the Yjs library. Cursors and changes from other people show up live.
Data on screen goes stale and users keep hitting refresh
We use WebSockets (a persistent connection between browser and server). The server pushes changes, and after a dropped connection the client reconnects and catches up on what it missed.
You worry it will fall over once user numbers grow
We plan for scale from the start: message queues, Redis to fan out events across servers, load tests before launch. For small products we often recommend a managed service so you don't pay for capacity you don't need.
What's included
- Scenario mapping: who talks to whom, roles and permissions
- Technology choice: custom WebSocket server or a managed service (Ably, Supabase Realtime, Liveblocks)
- Chat: direct and group rooms, read receipts, typing indicators
- Attachments: files and images in S3 storage with type and size checks
- Collaborative editing: cursors, user presence, version history
- Push and email notifications when a user is offline
- Message history and search in PostgreSQL
- CRM and website integration, plus an optional AI agent that replies in chat
- Load testing and connection monitoring
- Handover of code, accounts and access to you
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Chat in your product
A site or customer portal that needs customer-to-manager messaging
- Direct and group chats
- History, attachments, read receipts
- Email or push notifications
- Hook-up to your existing login
02
Live collaboration
Products with shared editing of documents, boards or forms
- Simultaneous editing via CRDT
- Cursors and user presence
- Version history and rollback
- Roles and access rules
- Chat or comments on objects
03
Real-time platform
SaaS with many roles, live dashboards and integrations
- Architecture built for growing load
- Live updates, chat and collaboration together
- Integrations: CRM, payments, AI agent
- Load tests and monitoring
- Documentation for your team
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Pilot with a KPI
We agree on one measurable goal, such as reply time to a customer. We build a minimal version and test it with real users.
Staged development
We work in iterations and show a working build every week. You pay in stages, after you accept each one.
Load testing
We simulate many users and dropped connections, then fix the bottlenecks before launch.
Launch and handover
We deploy on your accounts. All code, files and access belong to you under the agreed terms.
Scope and limits
- We don't promise full offline mode with complex data merging. That is a separate, larger scope.
- We don't include end-to-end encryption in the base package. It can be added, but it complicates search and moderation.
- We won't quote a concurrent-user limit until we've load-tested your actual setup.
FAQ
Custom server or managed service: which should I pick?
For chat with a few hundred users, a managed service is often cheaper and faster to start. A custom WebSocket server makes sense for complex logic, heavy traffic or strict data requirements. We compare both in the estimate.
How do you estimate the cost?
We prepare a quote after reviewing your brief and requirements. A first stage can cover: direct and group chats; History, attachments, read receipts. Scope, payment and schedule are agreed before work starts.
What do you need from me to start?
A description of scenarios and roles, examples of products you like, and access to your existing backend or API if you have one. We can design the interface, or you can supply finished mockups.
Can you add chat to an existing site or app?
Usually yes. We need to understand how your login works and where your data lives. After reviewing the code we'll tell you whether a modification is enough or chat should be a separate module.
How does this connect to AI agents and CRM?
Chat can sync to your CRM so conversations land on the customer record. An AI agent can answer common questions and hand tricky ones to a person. We scope that as a separate stage.
Who owns the code and accounts?
We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.