Case studies: our own products and client projects.

First, three apps of our own, with figures that update every day from their databases. Then client projects: company names on request, tasks and results described as they are.

Education · own product

1Study — platform for online schools

The brief: Give online schools in Kazakhstan their own app in the App Store and Google Play instead of a page on someone else's platform, with Kaspi payments straight to the school's account.

What we did: iOS and Android apps, a web version, school admin panel, courses, homework, cohorts, push notifications, white label, subscription billing through Kaspi, SEO storefronts for schools.

Result: 62 schools, 8,076 students, ₸1.57bn in turnover through the platform.

Next.js · Node.js · PostgreSQL · Swift · Kotlin · Kaspi Pay · Firebase

Hospitality and gaming clubs · own product

1Work — accounting for cafés, restaurants and gaming clubs

The brief: Show a venue owner net profit, till, stock and payroll on their phone without changing the POS system.

What we did: iOS and Android mobile app, integrations with Poloma and Senet POS systems, shifts and payroll, a staff wallet in Telegram, real-time reports.

Result: 8 venues, ₸246mn in revenue tracked through the product.

Fastify · PostgreSQL · Flutter · Telegram Bot API · Poloma API · Senet API

Events · own product

1Ticket — ticket sales on your own domain

The brief: Let concert organisers sell tickets on their own site, with no aggregator commission and no money on hold.

What we did: Ticketing site on the organiser's domain, Kaspi payments, e-tickets with QR codes, a door scanner, reports.

Result: 431 tickets and ₸6mn in paid orders at the first events; the open launch is in preparation.

Next.js · PostgreSQL · Kaspi Pay · QR

Industry · B2B

Procurement platform for an industrial group

The brief: Replace spare-parts procurement “by e-mail and WhatsApp” with a platform where suppliers see requests and submit offers.

What we did: B2B platform with supplier accounts, an RFQ site for spare-parts requests in three languages (Russian, Kazakh, English), automated request processing.

Result: Requests and offers in one system, a price history for every item, shorter procurement cycles.

Next.js · Fastify · PostgreSQL · Python

Client name available on request

Construction

Corporate website for a construction company

The brief: Present the company to tender boards and clients: projects, licences, equipment, contacts — fast and in three languages.

What we did: Design and development on Next.js, a project catalogue, an SEO structure built around queries by type of work, an enquiry form that delivers to a messenger.

Result: The site ranks in Google's top 10 for the region's target queries; enquiries from the site go straight to the director's WhatsApp.

Next.js · Tailwind · SEO

Client name available on request

Retail · equipment supplier

Catalogue website for a gate and barrier supplier

The brief: Win enquiries from search for queries like “gates Astana” and “buy a barrier”.

What we did: Catalogue with filters, pages for every category and city, a price calculator, SEO and Google Ads search campaigns.

Result: A steady flow of enquiries from organic search and ads; cost per enquiry below the niche average.

Next.js · SEO · Google Ads · Yandex Direct

Client name available on request

Distribution · textiles

Multilingual website for a textile distributor

The brief: Show brands and range to wholesale buyers from Kazakhstan and the CIS.

What we did: A three-language site with a brand catalogue, pages for B2B enquiries, a price-list request form.

Result: Enquiries from wholesale clients in three countries; faster manager responses thanks to structured requests.

Next.js · next-intl · Tailwind

Client name available on request

Media

Showcase website for a media group

The brief: Show advertisers the group's platforms, audience and formats — with animation, but fast.

What we did: Design and development on Next.js with Framer Motion, presentation pages for each platform, a media kit, a request form.

Result: PageSpeed above 90 on mobile despite heavy animation.

Next.js · Framer Motion · Tailwind

Client name available on request

Real estate · data centre

3D landing pages for a resort and a data centre

The brief: Sell investors and buyers on properties that do not exist yet: show the site and buildings in 3D directly on the website.

What we did: Interactive scroll-driven 3D scenes on three.js, a site map, presentation blocks, mobile optimisation.

Result: The presentation runs in a phone browser, with no apps to install and no heavy video.

three.js · GSAP · Leaflet · Vite

Client name available on request

Fintech

Personal finance app for iOS and Android

The brief: A native app for tracking expenses and income with sync across devices.

What we did: iOS on SwiftUI, Android on Jetpack Compose, a Node.js backend, publication in the App Store and Google Play.

Result: Two native apps on a shared backend; updates ship to both stores in sync.

SwiftUI · Jetpack Compose · Node.js · PostgreSQL

Client name available on request

Fitness

Fitness club landing page and loyalty programme

The brief: Bring in new clients from ads and keep existing ones with bonuses for visits.

What we did: Club landing page on Next.js, a SaaS loyalty platform with member accounts and bonus accrual, white label under the club's brand.

Result: Enquiries from the landing page go to the front desk's WhatsApp; the loyalty platform works as a standalone product for other clubs.

Next.js · Supabase · Tailwind

Client name available on request

Infrastructure · internal tools

Kaspi payment gateway, WhatsApp API and a Telegram bot builder

The brief: Stop rewriting the same things in every project: payments, messaging, bots.

What we did: A multi-tenant Kaspi Pay gateway, a WhatsApp messaging and chatbot service, a Telegram bot builder, an event service for the Meta Conversions API.

Result: Integrating Kaspi or WhatsApp into a client project takes days, not weeks — and that is built into our prices.

Node.js · Express · Prisma · Baileys · NestJS · Redis

Client name available on request

Why the client cases are unnamed

Some clients work with us under confidentiality clauses; others simply do not want competitors to see who their contractor is. So the public list shows the industry, the task and the result. If you need to see a specific site or talk to a client in your niche, write to us: we will show what we can and give you a contact for a reference.

What these projects have in common

All of them: a contract, an estimate before the start, weekly demos and code handed over to the client. Wherever there are sales — Kaspi. Wherever there is search — an SEO structure from day one, not “we'll add it later”. That is our process; more in how we work.

Questions

The short version.

Can I get a reference from one of your clients?

Yes. Tell us your niche — we will find a client with a similar task and ask their permission to share a contact.

Do you have cases in my industry?

Possibly. The list above is not everything. Describe the task and we will tell you whether we have done something similar and how it turned out.

Can I see the code?

Client project code belongs to the clients. The open examples of our work are our own products: 1Study, 1Work and this website.

Discuss a project

Tell us about the task and we will reply with an estimate and a timeline.

No introductory call required: describe the task in the form or in a messenger, we will ask a few clarifying questions and come back with an estimate. This usually takes one or two working days.

We reply during working hours, usually within a couple of hours.