BlackRevo Lumen: I built my company's system with AI. Version 1.402 in 8 weeks

BlackRevo Lumen is the company system BlackRevo runs on, and it went from its first line of code to version 1.402 in eight weeks with AI writing the code. Why we built instead of bought, how a problem a colleague reports becomes a live fix, and the 15 builds that stopped.

Also available in 中文

A dark sphere edged by a thin ring of warm light over a quiet desk at night.

Key takeaways

  • BlackRevo Lumen is BlackRevo's own company system. It is not for sale.
  • Three reasons to build instead of buy: speed, customisation, and cost.
  • Work began on 20 September 2026. Version History began at 1.0 on 27 September, and version 1.402 went live on 18 November 2026.
  • A colleague's problem can become a live fix the same day: four AI reviewers comment, a chair decides, and one button sends it to be built, tested and shipped.
  • In the first ten days staff filed 25 tickets, and the build lane shipped 16 of them.
  • Most failures were about timing, not code: a build stops when the code about to go live is not exactly the code that passed the tests.

What is BlackRevo Lumen?

BlackRevo Lumen is BlackRevo's own company system: one place where employees learn the company, apply for leave, file claims and run their projects, and where clients and creators each have their own door. It replaced the Word documents and Excel sheets that used to hold how the company works, which I wrote about in the question at a mamak table that started BlackRevo.

As of 18 November 2026 it covers:

  • hiring, the careers site and onboarding
  • leave, claims, attendance and payslips
  • projects and tickets
  • chat, sheets, a shared drive and email
  • meeting minutes
  • sales and invoices
  • SEO projects
  • separate portals for clients and creators

Lumen is the Latin word for light, and the unit that measures it. Its icon is an eclipse: the dark body is BlackRevo, and the light coming round its edge is Lumen.

Why did BlackRevo build its own system instead of buying one?

Three reasons.

Speed. When a bought system does something the wrong way for you, you ask the vendor and wait for their roadmap. With our own system the feedback loop is a day long, not a quarter. A problem a colleague hits in the morning can be fixed and live by the afternoon. On 17 November, Lumen had two dozen releases in one day.

Customisation. A bought system is a suit off the rack: it fits most companies a little and none of them exactly. Lumen is made to measure. It follows how BlackRevo actually works, our approvals, our words, our departments, instead of asking us to change how we work to suit the software. When the way we work changes, the system changes with it, often the same week.

Cost. It costs us a lot less than buying would. We have only the parts we use, and we pay nothing for the rest.

How fast was BlackRevo Lumen built?

The first line of code was written on 20 September 2026. A week later, on 27 September, Lumen's Version History began at 1.0, and from that day every release to production gets a written entry in it. The middle number goes up with each release that adds something. A fix adds to the last number, as in 1.99.3.

Version Recorded on
1.0 27 Sep 2026
1.50 6 Oct 2026
1.100 11 Oct 2026
1.150 18 Oct 2026
1.200 24 Oct 2026
1.250 3 Nov 2026
1.300 8 Nov 2026
1.350 15 Nov 2026
1.400 18 Nov 2026

By the morning of 18 November that was more than 500 releases, with at least one on 47 of the 50 days from 30 September. The busiest day was 17 November, with two dozen. The code had 2,868 saved changes, and 4,965 automated tests check it before a release goes out.

The speed comes from how the work is split: I decide and check, AI writes, and each piece is small enough to go live on its own.

How does a staff member's problem become a release?

Since 8 November 2026, Lumen has had tickets. This is the loop:

  1. Report. Anyone who uses Lumen presses the flag at the top of any page and writes what happened. The page, the version and the browser are filled in for them.
  2. Council. Four AI reviewers read the ticket, each from its own side: product, engineering, user experience, and security and data. A chair weighs what they said and writes a decision and a build brief.
  3. Decide. A person reads it and presses Build or Reject. A rejection needs a reason, and the person who filed the ticket reads it.
  4. Build. The build lane takes the ticket. AI on an office Mac writes the change, runs the checks, the build and the tests, reviews it and puts it live. The ticket shows each step as it happens: Building, Testing, Reviewing, Pushing.
  5. Shipped. The ticket moves to Shipped with the version it went out in, and the person who reported it is told.

In the first ten days, staff filed 25 tickets. The build lane shipped 16 of them, in 15 releases. Nobody wrote code by hand for those.

What went wrong

The lane ran 37 times between 8 and 18 November. 17 runs shipped, 15 stopped, 4 ended with a question instead of a change, and 1 was a test run.

  • Ten stops came at the last step. Lumen ships many times a day. A build takes time, and by the time it was ready, other releases had often gone live, so the code about to go live was no longer exactly the code that had passed the tests. The lane refuses to put untested code live, so it stopped, and the next run built again on top of the newest code.
  • Three runs did not finish their own steps. One ended without reporting back, one left out the file that puts it live, and one made no change at all.
  • Two runs went past the 90-minute limit and were stopped. Both were the same ticket, which took six runs before it shipped. The first ticket ever sent to the lane shipped on its third run, the same afternoon.
  • Four times the lane did not build at all. It could not find the problem in the code from what was written, so it asked one question back, such as which screen a reminder was on, instead of guessing.
  • Shipped has to mean fixed. Since 16 November, a build that changed nothing is never marked Shipped, and when the person who reported a problem says it is still not fixed, their words go into the next build.

What I took from it: the code was rarely the hard part. The hard parts were working out what a ticket really asked for, and keeping a busy main line safe while many changes wait to go live. A question back is better than a confident guess.

Who built BlackRevo Lumen?

I did, as the person who decides. I am BlackRevo's General Manager and co-founder. I decide what Lumen should do and check what comes back, and I run the company on it every day, which makes me its most demanding user. AI writes the code, and tests and reviews check it before it goes live. I wrote about this way of working in why I run my company on a Brain and a Hand.

Where can I see BlackRevo Lumen?

The official page is BlackRevo Lumen, the system BlackRevo runs on, on BlackRevo's website. BlackRevo Lumen is not for sale. It is BlackRevo's own system, used by our team, our clients and the creators we work with. There is a short profile on my ventures page. If you would like to know more about how it was built, I am happy to have a chat: get in touch.

FAQ

What is BlackRevo Lumen?

BlackRevo Lumen is the company system BlackRevo runs on. Employees use it for leave, claims, attendance, projects and learning the company, and clients and creators each have their own portal in it.

Who built BlackRevo Lumen?

Yap Pat Yih, General Manager and co-founder of BlackRevo, built it with AI. He decides what it should do and checks it, and AI writes the code. Work on it began on 20 September 2026.

What does the name Lumen mean?

Lumen is the Latin word for light, and the unit that measures it. The icon is an eclipse: the dark body is BlackRevo and the light around its edge is Lumen.

Can AI build a whole company system?

In our case, yes, with a person deciding and checking. AI wrote the code for more than 500 releases in eight weeks, but 15 of the build lane's first 37 runs stopped before shipping, and four times it had to ask a question first. The deciding and the checking stay with people.

Is BlackRevo Lumen for sale?

No. BlackRevo Lumen is BlackRevo's own system and is not sold to other companies. If you want to know more about how it was built, you are welcome to get in touch for a chat.