Working chatbot
A trained bot deployed on your website or platform of choice.
AI
Automation.
We build AI that does real work — assistants, chatbots and automations that answer from your own content and connect to your tools.
- Typical build
- 3–6 wks
- Monitoring and tuning
- 2–4 wks
- Data and accounts
- Yours
Overview
What is included
AI assistants and workflow automations that answer from your own content and plug into the tools you use.
- OpenAI
- LangChain
- Python
- Zapier
- Make
- Slack API
Tools we typically use; the stack is agreed per project.
- AI chat assistants
- Workflow automation
- Trained on your own content
- CRM and tool integrations
- Typical build
- 3–6 wks
- Monitoring and tuning
- 2–4 wks
- Data and accounts
- Yours
What you get
Not a deck. Working things.
Conversation flows
Designed dialogues for common scenarios and edge cases.
All of it lands in your accounts.
Your GitHub, your Figma, your domain — from day one, not at handoff. Everything above is yours to run, change, or take elsewhere.
Scope options
Three ways to start, scoped on a call.
Pick the one closest to what you need. On a short call we shape the scope with you, then send a written proposal with a fixed price per phase.
013 weeks
Quick bot
Test AI support on a single channel.
- Basic flows
- 1 channel
- Training data prep
- 2-week monitoring
026 weeks
Full assistant
A trained agent across your support channels.
- Custom training
- Multi-channel
- CRM integration
- Analytics
- 30-day tuning
03Scoped per project
Enterprise
Fine-tuned models with compliance and on-premise options.
- Fine-tuned LLM
- On-premise deploy
- Compliance review
- Dedicated support
Process
Four phases, each one signed off.
01Typically week 1
Discovery
A working session on your goals, customers and constraints. You get a written scope, a fixed price for each phase and a timeline to approve.
02Weeks 2–4
Design
Pages and key screens in a shared Figma file you can comment on at any time. Nothing is built until you approve it.
03Weeks 4–8
Build and test
Built in small pieces with a demo every week, and tested on real phones and browsers as we go. You review working software, not status reports.
04Launch, then 30–90 days
Launch and support
We launch, watch it closely and fix what comes up. Every build includes a support window, and ongoing work can continue on a flat monthly fee.
Week ranges are typical for a mid-sized website. Your proposal sets the real timeline.
How long does a project take?
It depends on scope. As a guide: a starter website takes 4 to 6 weeks and a larger site 6 to 10, an app MVP about 8 weeks and a two-platform app about 12, and a first AI assistant 3 to 6. Bigger work is scoped individually, and the timeline is fixed in the proposal before anything starts.
How does pricing work?
We talk it through on a call first. You then get a written proposal with a fixed price for each phase, agreed before anything starts. No hourly billing, so nobody is rewarded for taking longer.
Who owns the code, designs and accounts?
You do. The code, design files, domain, hosting and ad accounts sit in your accounts from day one, not at handover, so you can change supplier at any point.
How do revisions work?
You review real designs and working builds every week, and feedback inside the agreed scope is part of the fixed price. If a change alters the scope, we price it as a change and you decide before we do it.
What happens after launch?
Every build includes a support window for fixes and small adjustments: 30 or 90 days depending on the plan, and two weeks to a month of monitoring and tuning for AI work. After that, ongoing work can continue on a flat monthly fee.
Related work
All projects
Our product · 2026
Truplexy
Our own AI customer support platform: one assistant on every channel, one inbox for the team, a person when it matters.