Skip to content
Horulabs

Carve the work.

Horulabs is a technology consultancy. We map how your team works, keep your existing systems, and build or connect software to automate the routine.

Start a free consult

Today

  1. Requestby chat or email
  2. Copy — Step removedinto a spreadsheet
  3. Wait — Step removedno owner
  4. Re-type — Step removedinto another system
  5. Chase — Step removedstatus unknown
  6. Approveby email
  7. Recordby hand

Rework loop

Carved

  1. Requestone online form
  2. Reviewstatus visible to the team
  3. Approvemanager decides
  4. Recordsaved automaticallyAutomated

Steps removed

Illustrative example

Working systems, not slide decks.

  • EKLAIM

    Claims and paperwork

    Before

    1. Excel form — Removed
    2. Print — Removed
    3. Send the file — Removed
    4. Sign-off across sites
    5. Batch in finance — Removed
    6. Accounting entry — Removed

    After

    1. Online form
    2. Digital approval
    3. Invoice to OracleAutomated

    5 of 6 steps cut

    Claims run in one system: searchable, tracked through every stage, and posted to Oracle Fusion automatically, with no retyping.

    Internal at Sekar Laut. No public site.
    Read the case
  • Sekar Purchasing

    Procurement and approvals

    Before

    1. Paper form — Removed
    2. Send the form — Removed
    3. Sign-off across sites
    4. Batch in finance — Removed
    5. Accounting entry — Removed

    After

    1. Online form
    2. Rule-based approval
    3. Posts to AccurateAutomated

    4 of 5 steps cut

    Requests, approvals and orders run in one workflow, with a configurable approval hierarchy and purchase requests posted to Accurate Online automatically.

    Internal at Sekar Laut. No public site.
    Read the case
  • Nyusulapp

    Booking and offline operations

    Before

    1. Booking by chat — Removed
    2. Paper table book — Removed
    3. Cash till
    4. Re-typed takings — Removed

    After

    1. Online booking
    2. Table lock
    3. POS open bill

    3 of 4 steps cut

    One system for booking, table locks and the POS, with an open bill per table for F&B and other goods. It keeps working offline.

    Our own product. Built and run by Horulabs.

    Read the case

More work

Three systems for SURIMA.

One client in competitive mahjong, three products, each on its own site.

Ask how any of these was built. (opens in a new tab)

Map. Carve. Build.

Three stages. You keep the map, the shorter flow, and the working fix, with a handover.

  1. WORKAROUND

    Map

    01
    How
    We walk the task with the people who run it, from the first request to the final record.
    You get
    • A written map with the waits, repeated typing and handoffs marked.
  2. TWO STOPS REMOVED

    Carve

    02
    How
    Each step is checked for what it adds. Repeatable steps become automation candidates.
    You get
    • A shorter flow, with every removed step and the reason it went.
  3. TOOLS ALREADY IN USE

    Build

    03
    How
    We connect or adapt your tools, build where needed, and test on real cases before go-live.
    You get
    • The task running in your tools, plus a handover for the team.

The offer: Rintis

Not sure this fits? Start with a free conversation.

Rintis

One task, mapped, built, and in use.

For example: a claim, an approval chain, or a monthly report.

From $100

Scope agreed after the map

Ask about Rintis on WhatsApp (opens in a new tab)

A short description is enough. No employee records or attachments.

Today, typed twice

Recap sheet

Monthly report

Retyped by hand

Carved, entered once

Recap sheet

Monthly report

Automatic

Carried through
Illustrative example: a monthly report

Outside the edge

  • A second flow
  • An integration
  • A wider system

Scoped and quoted separately.

Send one workflow. We'll look at it with you.

Tell us the task that costs your team the most hours, and how it runs.

Before you send

A short description is enough. Please don't send employee records or attachments.

The first conversation is free, with no commitment.

  • 01

    Keep the tools. Build what's missing.

  • 02

    No fixed packages. Each workflow is different.

  • 03

    Map first. Software later.