Game client lead. Product builder.
Full-stack & AI engineer. Former game client lead, now Tech Lead at ONNI.
Explore my work01 /A little context
From game clients to running a business.
I’m Lawrence, a developer with 6+ years of software experience, including game client engineering and team leadership. As ONNI’s co-founder and technical lead, I now build the software around a business I help run.
My projects span storefronts, B2B ordering, membership systems, POS and video tools. I connect product decisions with implementation, then follow the actual workflow to check the result.
More about meWit Software · Outcomes from the work I led
View the full experienceGame Client Lead · Aug 2024–Jan 2026. Built a four-engineer core team and provided architecture mentoring to a separate four-engineer squad.
02 /Selected work
From the business side of the screen.
ONNI
The systems behind a real business.
EazyCut
A closer relationship between words and video.
POS System
From a single counter to a system for many stores.
More from the portfolio
03 /Working together
A useful next step for your business.
Websites & commerce
A clear path from discovering your business to placing an order. Websites, product catalogues and purchasing flows built around your customers.
- A good fit
- Brand sites, product catalogues, retail or wholesale ordering.
- Possible deliverables
- Page and content structure, purchasing flows, and agreed admin or payment integrations.
Business systems
Tools for the work behind the scenes: ordering, invoicing, delivery and day-to-day operations. Start with the process that needs attention.
- A good fit
- Repeated invoicing, manual reconciliation, order handoffs or access control.
- Possible deliverables
- Workflow maps, role and data rules, a working system and usage documentation.
AI applications
Explore one practical use case, make a working prototype, and evaluate it with real inputs. Keep human review where it matters.
- A good fit
- A defined task such as captions, information processing or reply drafts.
- Possible deliverables
- A usable prototype, sample-based evaluation, and human review and failure-handling flows.
From the first conversation to a usable handover.
Understand the work
Identify the users, the current process and where it gets stuck. Agree on the first scope, success criteria and inputs needed.
Build in stages
Get the essential flow working, then review usable versions together. Confirm the impact of external services, data migration or added scope as it comes up.
Verify and hand over
Check the agreed scenarios and prepare code, deployment and usage documentation. Define ongoing maintenance; cost and timing follow a clear scope.
A focused workflow is a good starting point. Scope, deliverables and maintenance arrangements are agreed for each engagement.
Every project starts with a conversation about the problem, the people and the scope. Find a useful starting point
Let’s talk04 /Field notes
Things learned along the way.
THE LAB / PLAY & LEARN
Ideas you can get your hands on.
Edit a caption, or take a sample order through its workflow.