Client tasks we turned into working systems
For each case - what was the problem, what we did, and what the business got. Some clients are under NDA, so we don't name them, but the numbers and approach are real.
Client
TenderCRM (our own product)
SaaS · Kazakhstan public procurement
3 sec
doc parsing
20+
platforms in one window
< 5 min
team onboarding
Problem
Tender teams in Kazakhstan track 20+ platforms manually in Excel and chats. Margins are "eyeballed," data gets lost, the team can't work in parallel.
What we did
- Walked through the process with 4 different distributor companies
- Designed a multi-tenant architecture with RLS isolation
- Built AI parsing of tender docs on Claude API - instead of an hour of manual entry
- All 6 Kazakhstan tax regimes, roles, audit log, analytics
Outcome
Live in production with real customers. Became the flagship case we show to new clients.
Client
Electronics distributor
Wholesale · 50+ people
−70%
manual actions
2.5×
order processing speed
0
lost orders per quarter
Problem
Orders came into 1C, logistics lived in Excel, client notifications went out manually from Telegram. Between the systems - copy-paste and lost rows.
What we did
- Built a layer between 1C and ops via webhooks
- Shipped a single admin: order → status → delivery → feedback
- Automatic client notifications (SMS + email) per status
- Real-time dashboard for revenue and overdue items
Outcome
The ops team stopped working evenings. Errors between 1C and logistics dropped to a handful per month.
Client
Services company
B2B services · branched franchise network
real-time
vs weekly reports
99.2%
uptime over 6 months
−3 days
to assemble quarterly reports
Problem
20+ branches tracked clients in different spreadsheets. Central office saw numbers with a week's delay; quarterly reports were assembled by hand from emails.
What we did
- Unified CRM with roles: branch / region / central office
- Row-level security so branches don't see each other's clients
- Accounting sync - invoices and acts generated automatically
- Live dashboard for leadership, filterable by region
Outcome
Central office sees the state of the whole network in real time. Quarterly reports take 5 minutes instead of 3 days.
Client
SaaS startup
Education · MVP → first 1,000 users
12 weeks
from idea to launch
1,000+
first users
< 0.1%
Sentry error rate
Problem
Founders knew the market but had no technical team. They needed a working MVP to go to investors - not a "prototype on their knees" but a product that could actually carry the first customers.
What we did
- Fast discovery - picked 3 core features for the MVP and cut the rest
- Stripe for subscriptions, OAuth + magic link for sign-in
- Multi-tenant and role groundwork so no rewrite after the raise
- Sentry + analytics from day one
Outcome
The MVP carried the first user wave without incidents. The founders went to investors with a live product, not slides.