GeekScience +65 8151 6598

Build. Automate. Ship

Custom software for Singapore SMEs. Internal tools, practical automation, and the judgement to know when not to build.

Build Work, in order
01 / Work ( 4 )

What we build.

  1. 001 / Apps

    Custom applications

    Internal tools your team will actually use, replacing the spreadsheet that became the system, the order log three people update by hand, and the job board living in WhatsApp. They run on the devices you already have.

    • A delivery schedule that dispatch, drivers and the office all read at once.
    • A stock count that works on the warehouse phone and updates the sheet accounts use.
    • A quotation tool that keeps last month's errors out of this month's file.
  2. 002 / Automation

    Practical AI

    Automation that removes busywork rather than demonstrating a chatbot. AI earns its place when it takes a repetitive job off a person, and you get a straight answer whenever simpler software would do the same work.

    • Supplier invoices read and posted, with the exceptions flagged for a person.
    • The twenty questions customers always ask, drafted for staff to approve and send.
    • Orders arriving by chat and email collected into one queue.
  3. 003 / Delivery

    Production-ready software

    Software that ships. Hosted, backed up, logged, and handed over with documentation the next engineer can read. You keep the code and the accounts.

  4. 004 / Advisory

    IT & AI consulting

    Scope before build. What the problem actually is, what off-the-shelf software already covers, and what is worth building. Sometimes the answer is a subscription you already pay for and no project at all.

02 / How ( 4 )

From first message to working software.

  1. 01

    Tell us the problem

    A couple of paragraphs: what you do, where the time goes, and what you use today.

  2. 02

    Scope in plain language

    A fixed scope and a price for it. If buying beats building, the reply says so.

  3. 03

    Build in the open

    You see working software early, not at the end. Changes are conversations, not change requests.

  4. 04

    Ship and hand over

    It goes live on your accounts, with the code, the documentation and a direct line for what comes next.

One engineer, from the first message to the handover.

03 / Founder ( 1 )
LexFounder

Twelve years of production software.

GeekScience is led by Lex, a full-stack engineer with twelve years inside multinationals, now working independently in Singapore.

Every project is scoped, built and shipped by the founder. That is the point of a small studio: nothing sits between the problem and the person solving it, and nobody is paid to build more than you need.

LexFounder, GeekScience

04 / Contact ( direct )

Send one real problem.

Describe the job that costs your team hours every week, in your own words. No brief, no requirements document. Whichever way you reach us, it comes straight to the founder.