How do we get started?

Send a short description of your project by WhatsApp or email. We usually reply within 24 hours and arrange an initial call to understand the requirement and check we're a good fit. You'll then receive a proposal setting out scope and pricing.

How long does a project typically take?

A typical brand website takes 3–6 weeks, and a more complex web application can run 2–4 months. The actual timeline depends on scope, how ready your content is and how quickly feedback comes back — projects with content prepared upfront move noticeably faster.

How much does it cost?

Website packages start at RM1,200 — RM1,200 for a single page, RM2,500 for up to five pages, RM3,500 for up to ten, all with 30 days of post-launch bug support. Custom systems — e-commerce, booking, membership, internal operations — carry no starting figure, because the scope varies too widely for one to mean anything. Those begin with a free diagnostic covering scope, process complexity, integrations and long-term support; the quotation follows, and we explain how the figure was reached.

What types of projects do you take on?

Digital transformation consulting, websites, custom systems (ERP, CRM, membership, booking, inventory, internal operations), AI automation, mobile apps, and the ongoing partnership that keeps them running afterwards. We're selective — and if we think now isn't the right time for a piece of work, we say so.

What if I only have an idea, not a full specification?

That's fine, and it's a common starting point. The Discover stage exists precisely to turn an idea into a clear scope — we work through the goal, the users and the priorities together before deciding what gets built and in what order.

What happens after launch?

Every project includes a post-launch support period for bugs and technical issues within the agreed scope; the length is stated in the quotation. After that it can become an ongoing partnership — monthly or annual — covering maintenance, monitoring and continuous improvement. New pages, new features and redesigns are additional work and are identified as such.

What if we're not ready for a system or AI yet?

That's fine, and it's often the better starting point. The transformation ladder is a maturity map, not a sales funnel — automating processes that haven't been mapped usually wastes the investment. We work out which stage you're actually at, then tell you what comes next and what to leave alone for now. "You don't need this yet" is an answer we're willing to give.

Can we work together remotely?

Yes — the entire process runs online. Kokiyo Studio is based in Malaysia and works with clients locally and overseas; communication, design reviews and feedback all happen remotely.

Who actually works on my project?

Leon Lim, the founder, works on it directly, from conversation through design and development. The work starts with understanding the business problem, not a proposal — so nothing is handed off or lost in translation, and you always know who to ask.

Why ERP Projects Fail Before the Build Begins

ERP projects are often described as software implementations, but the difficult work happens before configuration. Different people may have different definitions of an order, an available stock figure or an approved purchase. The software cannot choose between those definitions for the business.

A useful pre-build exercise follows one real transaction from beginning to end. Who creates it? What information is required? Which system is the source of truth? What happens when something changes? The gaps and exceptions are more valuable than a feature checklist.

Only after the process is understood should the team decide what belongs in the core system and what can remain simple. This order reduces rework and gives the eventual system a chance to support the business instead of forcing the business to imitate the software.