What can we build for you?
The products businesses ask for most — each with typical features, honest ways to build it and a realistic first-version timeline. Your idea doesn't have to match a card.
16 / 16
Online store & e-commerce
Shops and brands that sell through Facebook pages and chat today and want a proper store with orders, stock and payments in one place.
Typical features
- Product catalogue with photos, variants and stock
- Cart and checkout with Lao QR or card payment
- Prices in LAK (and other currencies if needed)
- Order tracking and notifications by chat or email
- Admin panel for products, orders and simple reports
- Lao and English storefront
Ways to build it
- Web-first — Next.js + PostgreSQLA fast, search-friendly store you fully own, ready to add an app later.
- Store + app — Flutter + SupabaseOne codebase for the website and the Android/iOS app, with a shared back-end.
- Hosted platform — Shopify or WordPressStart selling sooner on a ready platform; we set it up and connect local payments where possible.
Typical timeline: 4–10 weeks for a first versionStart this projectBooking & appointments
Salons, spas, clinics, tutors, sports courts, repair shops and any service business that takes bookings by phone or chat.
Typical features
- Online calendar with available time slots
- Booking, reschedule and cancel by customers
- Reminders by SMS, Telegram, WhatsApp or email
- Staff schedules and service lists
- Deposits or prepayment by Lao QR
- Daily bookings dashboard for the owner
Ways to build it
- Fast MVP — Flutter + SupabaseCustomer app and staff view from one codebase, with realtime updates.
- Web-first — Next.js + PostgreSQLA booking page that works in any browser, with no app install needed.
Typical timeline: 4–8 weeks for a first versionStart this projectFood ordering & delivery
Restaurants, cafés, cloud kitchens and delivery services that want their own ordering channel instead of relying only on chat messages.
Typical features
- Menu with options, add-ons and opening hours
- Order in the restaurant by table QR, or for pickup and delivery
- Kitchen screen with order status
- Rider assignment and live delivery status
- Lao QR payment and daily sales summary
Ways to build it
- Fast MVP — Flutter + SupabaseCustomer, kitchen and rider apps sharing one realtime back-end.
- Web-first — Next.js + PostgreSQLTable-QR ordering in the browser first; native apps can follow.
Typical timeline: 6–12 weeks for a first versionStart this projectMulti-vendor marketplace
Founders who want many sellers or service providers to list on one platform, with buyers searching, ordering and paying in one place.
Typical features
- Seller sign-up, profiles and listing management
- Search, filters and categories for buyers
- Orders, commissions and seller payouts
- Ratings and reviews from real buyers
- Admin moderation and dispute handling
Ways to build it
- Web-first — Next.js + PostgreSQLSearch-friendly marketplace website with an admin panel; apps added once it grows.
- Fast MVP — Flutter + SupabaseValidate the idea quickly with one app for buyers and sellers.
- Your cloud — AWS, Azure or Google CloudFor larger launches that must run in a specific cloud account.
Typical timeline: 10–20 weeks for a first versionStart this projectLoyalty & membership
Cafés, retail chains, gyms and clubs that want to reward repeat customers and replace paper stamp cards.
Typical features
- Digital member card with QR code
- Points, stamps or tier levels
- Rewards, vouchers and birthday offers
- Push notifications for promotions
- Member list and visit reports for the owner
Ways to build it
- Fast MVP — Flutter + SupabaseMember app plus a simple staff scanner, sharing one back-end.
- No-install — web app (PWA)Members open their card in the browser; nothing to download.
Typical timeline: 4–8 weeks for a first versionStart this projectE-wallet & payments with Lao QR
Merchants, platforms and fintech teams that need to accept, check or reconcile Lao QR payments inside their own product.
Typical features
- Generate Lao QR (EMVCo) codes with amount and reference
- Read and validate payment QR codes
- Match payments to orders and flag mismatches
- Merchant dashboard and exportable reports
- Connection to a bank or wallet API once access is granted
Ways to build it
- Add to your app — API + SDKA small payment service your existing app or website calls.
- Fast MVP — Flutter + SupabaseA merchant app with QR generation, history and reports.
Typical timeline: 4–10 weeks for a first version, depending on bank accessStart this projectPOS & inventory for shops
Shops, mini-marts, pharmacies and wholesalers that track sales and stock in notebooks or spreadsheets.
Typical features
- Fast sales screen on a tablet, phone or PC
- Barcode scanning and receipts
- Stock levels, low-stock alerts and purchase orders
- Several branches and staff roles
- Works offline and syncs when back online
- Daily, monthly and product sales reports
Ways to build it
- Tablet-first — Flutter + SupabaseOffline-capable POS app with a shared online back-office.
- Web-first — Next.js + PostgreSQLRuns in the browser on any device, including old PCs.
- Windows desktop — .NETFor shops that already use Windows PCs and receipt printers.
Typical timeline: 6–12 weeks for a first versionStart this projectHR, attendance & payroll
Companies, factories and NGOs that manage attendance, leave and salaries on paper or in spreadsheets.
Typical features
- Clock-in and clock-out by phone with location or QR
- Leave requests and approvals
- Shifts, overtime and holidays
- Payroll calculation and payslips in LAK
- Employee records with role-based access
- Reports and exports for management
Ways to build it
- Fast MVP — Flutter + SupabaseStaff app and manager dashboard; the same approach as our Smart HR app.
- Your stack — .NET or JavaWhen it must fit into existing company systems and servers.
Typical timeline: 6–12 weeks for a first versionStart this projectCRM & sales pipeline
Sales teams and service businesses that lose track of leads across phone calls, chat apps and spreadsheets.
Typical features
- Contacts, companies and conversation history
- Sales pipeline with stages and follow-up tasks
- Leads captured from website forms and chat
- Quotes and simple invoices
- Team performance and forecast reports
Ways to build it
- Web-first — Next.js + PostgreSQLA CRM shaped around how your team actually sells.
- Extend what you have — Odoo, HubSpot or SalesforceCustomise and connect an existing CRM instead of building one from scratch.
Typical timeline: 6–12 weeks for a first versionStart this projectBack-office & ERP-lite dashboards
Growing companies whose orders, purchasing, finance and reports live in many separate spreadsheets.
Typical features
- One dashboard for the numbers that matter
- Purchasing, sales and expense records
- Approval workflows with history
- Role-based access for each department
- Import from Excel and export to PDF or Excel
Ways to build it
- Web-first — Next.js + PostgreSQLA secure web back-office that grows module by module.
- Fast MVP — Supabase + admin UIGet your data into one place quickly, then refine the screens.
- Microsoft shops — ASP.NET Core + SQL ServerWhen your company already runs on Microsoft systems.
Typical timeline: 8–16 weeks for a first versionStart this projectInternal tools & automation
Teams that repeat the same manual steps every day — copying data, renaming files, building reports or checking records.
Typical features
- Windows or cross-platform desktop tools
- Scripts that import, clean and merge data
- Scheduled reports sent automatically
- Connections between the systems you already use
- Works offline where needed
Ways to build it
- Windows tool — .NETA native Windows app that fits an existing Microsoft setup.
- Scripts — Python or PowerShellFast, low-cost automation for data and file tasks.
- Cross-platform — Electron or TauriOne desktop app for Windows, macOS and Linux.
Typical timeline: 2–8 weeks for a first versionStart this projectSchool & e-learning
Schools, training centres and tutors that manage classes, students and learning materials by hand.
Typical features
- Student, class and teacher records
- Timetables, attendance and grades
- Courses, videos and quizzes online
- Announcements to parents and students
- Fee tracking with Lao QR payment
- Lao and English interface
Ways to build it
- Fast MVP — Flutter + SupabaseApps for parents, students and teachers with one back-end.
- Web-first — Next.js + PostgreSQLA learning portal that works on any device without installing.
Typical timeline: 8–14 weeks for a first versionStart this projectLogistics, ride & fleet tracking
Delivery companies, transport services and businesses with vehicles that need to know where jobs and drivers are.
Typical features
- Driver app with jobs and live location
- Dispatcher map and job assignment
- Proof of delivery with photo and signature
- Customer tracking link and notifications
- Trip, distance and fuel reports
Ways to build it
- Fast MVP — Flutter + SupabaseDriver and customer apps with realtime locations and maps.
- Native — Kotlin + SwiftWhen background location and battery use must be tuned per platform.
Typical timeline: 8–16 weeks for a first versionStart this projectAI customer-service chatbot
Businesses that answer the same customer questions all day on their website, Facebook, Telegram or WhatsApp.
Typical features
- Answers from your own price lists, FAQs and policies
- Website chat, Telegram and WhatsApp channels
- Hand-over to a person when the bot is unsure
- Lao and English conversations
- Conversation history and usage limits for cost control
Ways to build it
- Managed AI — LLM APIs + RAGGrounded answers from your documents using commercial AI models.
- Private AI — open-source modelsRuns on your own server when data must not leave it.
Typical timeline: 3–8 weeks for a first versionStart this projectDocument AI: search, OCR & Lao text
Offices, banks, NGOs and government-facing teams with large archives of documents, scans and forms in Lao and English.
Typical features
- Search documents by meaning, not just keywords
- Ask questions and get answers with sources
- Text extraction from scans and photos (OCR)
- Summaries and key-field extraction from forms
- Access control by team or document type
Ways to build it
- Managed AI — LLM APIs + RAGQuickest route to useful answers over your documents.
- Private AI — open-source models + vector databaseEverything stays on your own infrastructure.
Typical timeline: 4–10 weeks for a first version, after a sample-data checkStart this projectCompany website & CMS
Companies, NGOs and professionals who need a modern, fast website they can update themselves.
Typical features
- Responsive design for phones, tablets and desktops
- Lao and English pages
- Content editing without a developer
- Contact forms, chat buttons and maps
- Search-friendly structure and fast loading
- Analytics that respect visitors' privacy
Ways to build it
- Fast & modern — Next.js + headless CMSVery fast pages with an easy editor for your team.
- Familiar editor — WordPressThe widely used CMS your staff may already know.
- Visual builder — WebflowDesign-led pages your marketing team edits visually.
Typical timeline: 2–6 weeks for a first versionStart this project
Something else?
Tell us your idea. If it can be built with software, we'll suggest a way to build it and an honest first-version plan.
Have an idea? Your first build can be free.
A limited number of free first builds each quarter, with scope agreed in writing. You own everything we make.