Our work
Systems that went into daily use.
Selected web systems, e-commerce platforms, SaaS tools, and consultation work, each shaped around an operational problem someone was already living with.
Selected work
Four projects, in their own words.
Filter by category, then open a project for the problem, the approach and what changed.
DoubleOne · 2023
DoubleOne E-Commerce Platform
- The problem
- Orders were previously handled through WeChat and WhatsApp, creating repetitive manual coordination, higher response workload, and limited visibility during busy periods.
- What we did
- We designed a Laravel and React.js platform with a clearer storefront, secure Stripe payment flow, and backend tools for product, inventory, and order management.
- Checkout Flow
- Streamlined
- Manual Coordination
- Less
- Order Management
- Clearer
- Laravel
- React.js
- Stripe
- MySQL
Zabulongmart · 2024
Zabulongmart E-Commerce System
- The problem
- Manual ordering through messaging platforms made product updates, customer coordination, and order tracking harder to manage as the catalog grew.
- What we did
- We developed a performance-focused commerce platform with cleaner product browsing, backend management tools, and flexible architecture for future operational improvements.
- Product Updates
- Simpler
- Manual Communication
- Less
- Shopping Experience
- Improved
- Laravel
- React.js
- Stripe
- MySQL
ShareURL ONE · 2025
ShareURL ONE Platform
- The problem
- Creators and small teams often manage links, QR codes, analytics, and simple landing pages across separate tools, creating extra setup and reporting work.
- What we did
- We architected a modular SaaS platform with smart link management, QR generation, centralized analytics, and OneBio page tools in a single dashboard.
- Links Generated
- 10K+
- User Feedback
- 4.8/5
- Marketing Workflow
- Unified
- Laravel
- React.js
- Stripe
- MySQL
PeerHive · 2024
PeerHive Performance Optimization
- The problem
- The platform experienced backend slowdowns and lacked clear visibility into which technical issues were affecting performance.
- What we did
- We reviewed backend behavior, identified performance bottlenecks, optimized key areas, and provided architectural recommendations for future scaling decisions.
- Backend Response
- Improved
- Operational Friction
- Reduced
- Scaling Roadmap
- Clear
- Backend Audit
- Performance Tuning
- Architecture Review
Next step
Tell us what you are running today.
Send us what you have — a system, a spreadsheet, a half-finished build — and we will tell you honestly what is worth keeping.