loading...
Jigso integrates with email, Salesforce, Zendesk, and Slack, then batches and prioritizes notifications – reducing the context-switching that costs employees significant productive hours daily.
ENTRY ANGLES
Unified platform combining intelligent notification management with unified data access across enterprise tools · Vertical-focused product targeting acute notification overload in specific enterprise workflows (e.g., customer success teams) · AI-mediated information flow layer built on foundation model APIs with connectors to existing corporate tools
VERTICALS
CAPABILITIES
Integration layer / connector infrastructure for enterprise tools (Slack, Salesforce, Zendesk, Google Workspace), Foundation model API integration for intelligent information filtering, Product design for notification and information flow management
Notifications are the productivity tax that nobody tracks. An employee is deep in focused work, a Slack message appears, then a Salesforce update, then a calendar reminder – and the original task is gone. Getting back to it costs time and cognitive overhead that never shows up on a timesheet but compounds across every employee, every day.
Jigso's AI assistant, Sidekick, is designed to absorb that tax. It integrates with the corporate tools a company already uses – email, Salesforce, Zendesk, calendars, Slack, and others via pre-built connectors – and becomes an intermediary between the raw notification stream and the actual employee. Instead of getting raw alerts from every service, users interact with Sidekick in natural language and pull information on demand.
The product runs as a Slack bot today, with mobile apps and a Microsoft Teams integration planned. Three core usage patterns cover most of the value.
The first is notification filtering. A user tells Sidekick what's important right now – a key account name, a specific metric threshold, a project tag – and only alerts matching those criteria reach them. Everything else is buffered.
The second is on-demand querying. Rather than maintaining notification subscriptions across every tool, users simply ask Sidekick what they want to know. "How many open Jira tickets does each of my team members have?" – Sidekick fetches the data and returns a table, without requiring the user to switch apps.
The third is digest generation. Sidekick can summarize message threads, Slack channels, or tagged conversations and surface the key points. When something in the digest requires follow-up – say, a flag that an important client had a complaint – the user can ask Sidekick for context on what happened and what was promised in response, without reading through the entire thread.
Jigso spent 2022 refining the product with an early cohort of interested companies. That work produced 50 initial enterprise clients. The company has now closed its first funding round at $7.5 million.
A [recent review covered liftOS](/review/pljus-20-rabochego-vremeni-iz-niotkuda), which tackled a related productivity drain: the cognitive cost of switching between applications. The numbers from that piece are striking – employees can switch between apps and browser tabs up to 1,200 times per day, losing roughly 9% of working hours to context-switching alone. LiftOS proposed keeping all tools accessible as widgets on a single screen.
Notifications add a second layer of interruption on top of that. Unlike app-switching, which at least happens within the logic of planned work, notifications inject external agenda items at random intervals. The more conscientious an employee is about staying on top of things, the more alerts they've enabled – which means the more their work is interrupted. That's a genuine paradox: the most engaged employees are often the most distracted.
Estimates suggest notification-driven interruptions cost somewhere between 10–20% of working time, likely more for senior employees managing multiple workstreams. Against a backdrop where companies have been cutting headcount and expecting the remaining team to absorb more work, that's an obvious place to recover capacity without adding headcount.
The timing also benefits from what's happening in AI. The intelligence needed to parse natural language queries, understand context, and filter meaningfully across heterogeneous data streams wasn't practically available at enterprise scale two years ago. It is now.
The category – AI-mediated information flow inside companies – is early and wide open. Jigso spent a year validating that enterprises will pay for this, which removes the most important unknown for anyone building in adjacent territory.
The product can be replicated at this stage without starting from scratch. The integration layer – connectors to Slack, Salesforce, Zendesk, Google Workspace, and similar tools – is the core infrastructure investment, and the patterns for building it are well documented. The intelligence layer now runs on foundation models that are accessible via API.
One observation worth acting on: Jigso and liftOS are solving complementary halves of the same problem. LiftOS reduces switching cost between planned tasks; Jigso reduces interruption from unplanned notifications. Both center on integration with the same underlying corporate tools. A combined platform that handles both – unified data access and intelligent notification management in a single product – would address the full scope of the productivity problem rather than one slice. The integration core is essentially the same; the product surfaces would serve the same user.
The entry point that makes the most sense is a focused vertical: pick a category of enterprise tool where notification overload is most acute (customer success teams drowning in Salesforce and Zendesk alerts, for example), build tight integrations there first, and expand the scope once the core behavior is established.