We're building Cursor for sales - an AI assistant doubling sales productivity by handling prospecting, CRM updates, meeting prep, and follow-ups.
Backed by founders & operators @ Lovable, OpenAI, Neo4j, Creandum. Pre-seed. Shipping fast.
What you’ll do:
- Own UI/UX of an AI sales assistant end-to-end: research, design & final code
- Develop fast, accessible, and delightful to use pixel perfect interfaces across web, mobile & desktop
- Ship fast, test ideas with users & use data to kill your darlings
Current stack: React, TypeScript, Tailwind
Comp: Competitive base + meaningful early equity (flexible structure)
Apply: [email protected] — LinkedIn, GitHub/portfolio, why Spiich, and your proudest shipped work.
We're building Cursor for sales - an AI assistant doubling sales productivity by handling CRM updates, meeting prep, prospecting and follow-ups.
Backed by founders & operators @ Lovable, OpenAI, Neo4j, Creandum. Pre-seed. Shipping fast.
Founding GTM - Own revenue and customer success E2E
- B2B SaaS sales experience beating quota (2-3 years, or less if you're exceptional)
- Full-cycle deals from SMB → Mid-market (€10k–€200k ARR)
- Build pipeline and playbook from scratch
Fullstack Engineer - Work on the core product
- 1-3 years experience building at high velocity - TypeScript (Node + React), PostgreSQL, graph databases
- Own features E2E: voice/text AI interfaces, knowledge graphs, CRM integrations, real-time infrastructure
Comp: Flexible package (base + equity)
Apply: [email protected] - Include LinkedIn, why Spiich, proudest achievement, GitHub (engineering), and quota attainment (GTM)
spiich.ai
I've reached a point where tweaking system prompts, tool docstrings, and Pydantic data type definitions no longer improves LLM performance (tool args accuracy and speed). I'm considering a multi-agent setup with smaller fine-tuned models, but I'm concerned about latency and the potential loss of overall context (which was an issue when trying a multi-agent approach with out-of-the-box...