Skip to content
Horizon is live. Read it

Start a project

Tell us what's costing you hours.

We'll come back with what it takes to build, what it takes to run, and whether we're the right people for it.

Replies within 24 hours. Both numbers reach a founder, not a sales desk.

Who you are
01

Who you are

So we know who we’re replying to.

What’s breaking
02

What’s breaking

The more specific the better. Hours lost, orders missed, numbers that don’t reconcile.

Shape of it
03

Shape of it

Rough is fine. This is to work out whether we’re the right people, not to quote you.

Send it

Both go to a founder, not a sales desk. Nothing is stored on this site: the brief below is composed in your browser and handed to your own mail or WhatsApp app.

New project brief via lewix.my

01 Who you are

02 What’s breaking

03 Shape of it

Questions people ask first

What does it cost?
Projects start at RM 8,000. That is a floor rather than an average — what a system actually costs depends on how much of the operation it has to cover — but it is a real number, and we would rather you had it before spending an hour on a call finding out.
What do you actually build?
The operational software a business runs on: inventory, invoicing, dispatch, production scheduling. The systems that stop the company when they stop. Not marketing sites.
How does a project start?
Discovery first, where we learn how the business actually operates. Then architecture — schema, API structure, user flows — before any interface gets built, so there are no surprises during the build.
Will it work with the software we already use?
That’s usually the point. Where the books are already in SQL Account, the system reads from there directly rather than asking anyone to type the same figure twice.
Where does it run?
On infrastructure we manage ourselves, not a platform we’d have to file a ticket with when something needs fixing. SSL, monitoring and backups are part of the deployment, not an add-on.
What happens after launch?
Launch is the start. Systems get second versions, new modules and audits as the business changes, and we’re still in the codebase long after handover.
What don’t you take on?
Work where nothing is measurably broken. If there isn’t a real operational cost to fix, we’re the wrong people and we’ll say so early.