01 / IMPLEMENTATION
Build something useful.
Small, defined automations and integrations that solve a real operational problem.
One scope. One deliverable. →
An independent engineering workshop / AI & automation
We make work less work.
We find the repetitive work worth automating, build a sensible solution around your existing tools, and show your team how to run it.
A small team. Short projects. No unnecessary fuss.
People doing the actual work In your Slack or Teams Built to hand over No platform to buy
01 / What we makeThe sort of stuff
The sort of stuff
we can fix.
Most teams have useful work buried under copying, chasing, checking and updating. Here are a few places we tend to look first. These are examples, not off-the-shelf products.
01
Find the sales leads you forgot about.
Review old emails and CRM activity, spot conversations that went quiet and prepare follow-ups for your team to approve.
SALES / EMAIL / CRM
02
Clean up the CRM without a cleanup week.
Find duplicates, flag outdated details, check who changed jobs and propose updates before anything gets written back.
REVENUE OPERATIONS / DATA
03
Know what actually happens on calls.
Review recorded calls and support conversations, surface recurring issues and give managers a useful QA starting point.
CUSTOMER EXPERIENCE / QA
04
Stop assembling the same report every Friday.
Pull the numbers from your existing tools, reconcile them and deliver a report people can use, without the usual spreadsheet ritual.
OPERATIONS / REPORTING
05
Give the support inbox a first pass.
Sort requests, draft straightforward replies and route unusual cases to a real person. Start with a narrow, testable scope.
SUPPORT / WORKFLOWS
06
Ask better questions of your data.
Make a trusted slice of your database searchable in plain English. Begin read-only; add changes only when it's safe and useful.
INTERNAL TOOLS / DATA
02 / The approach
We're not here to give you another system to worry about.
Your team knows the business. We know how to take a repetitive process apart and put it back together so it does less damage to everyone's calendar.
✓ We use the tools you already have wherever that makes sense.
✓ We involve whoever owns access, security and infrastructure.
✓ We think about failures and maintenance before handover.
A note from the workshop / 002
“If a simple integration does the job, we're not going to build you an AI agent.”
[ preferred outcome ]
less to maintain
more time to do actual work
03 / How we workA small project
A small project
should stay small.
Start with one problem. We agree on a deliverable, build it, test it with real cases and hand it over. No long strategy engagement required.
01 / UNDERSTAND
Show us the annoying bit.
We look at the workflow, the tools, and what a useful result would be.
02 / SCOPE
Agree on what we'll build.
Clear boundaries, a fixed project fee where practical, and a plan everyone understands.
03 / BUILD & TEST
Make it work in real life.
We implement, handle the edge cases and test with your team before launch.
04 / HAND OVER
Leave the keys with you.
Documentation, a walkthrough and a maintainable solution. More help only if you want it.
Contained workflows can often be delivered in a few weeks. We won't promise a timeline until we've seen the problem.
04 / More ways to work togetherSometimes you need
Sometimes you need
a builder. Sometimes
another opinion.
We can help before, during or after implementation. The point is to leave your team more capable, not more dependent.
02 / SECOND OPINION
Get another pair of eyes.
Architecture, tools, operating cost, reliability. We'll tell you what we'd keep and what we'd change.
No obligation to rebuild. →
03 / WORKSHOPS
Help your team learn the ropes.
Practical sessions on AI tools, workflows and the systems your people actually use.
Useful skills, not a slide marathon. →
05 / Who's behind it
You'll talk to the people doing the work.
We're a small, independent team combining hands-on engineering with experience running the kinds of operations we help improve. No layers of account management.
The backgrounds below describe work from before A Bit of Sense. They are not presented as clients or projects of this new firm.
IP
Ivan Pushkin
Operations and delivery. Previously led a customer operations organisation of roughly 400 people and helped build a conversational AI business.
I
Ilya
Engineering and automation. Builds practical systems across APIs, data, prospecting tools and everyday operational workflows.
Real portraits, full biographies, relevant examples and verified professional links to be added before launch.
06 / A few fair questionsBefore we
Before we
get started.
Do we need a technical team?
Not necessarily. We can build relatively self-contained workflows around your existing tools. Where a project touches sensitive data, production systems or access policies, we'll work with the person responsible for them.
What if we already have a CTO or developers?
Good. We're not trying to replace them. We can take on a contained business workflow, document our work and hand it over to the people who will maintain it.
Do we need to sign up for a retainer?
No. We can agree on a project, finish it and hand over the result. Ongoing support and further projects are available when useful.
Does every solution need AI?
Definitely not. Sometimes the simplest solution is a script, an existing feature in your CRM or a better process. We'll make the technical trade-offs clear.
Can you start with something small?
That's our preferred way to begin. Show us one repetitive task, and we'll help decide whether it can become a short, fixed-scope project.