A closed laptop, notebook and pen on a studio workbench in warm evening light

A development studio, not an agency

About Null Lines

We build custom web applications and mobile apps from 7 Siglap Drive, Singapore — for founders, SMEs and enterprise teams here and across the region.

What we are

A software studio in Singapore. We write and maintain the code our clients run their business on.

We're a development studio, which means we build software rather than sell a platform or a licence. Our work is custom: a web application shaped around your process, a mobile app for your users, an integration between systems that don't natively speak to each other. We're not an advertising agency or a design house with a development arm attached.

That focus is deliberate, because building and maintaining software is a different discipline from running campaigns, and trying to do both usually means doing one badly. The practical effect for you is simple: the people who scope your project are the people who build it, and nobody hands your code to a team that has never met you.

Null Lines Pte Ltd is registered in Singapore and works on web and mobile application development end to end — discovery, build, launch and the changes that come after. Custom web application work is the core of it; mobile and integration projects usually sit alongside an existing system rather than replacing it.

How we approach engineering

We care about the parts of a project that don't show up in a screenshot. These are the standards we hold a build to before it goes near a client.

and the parts we still fix six months later

  • Data models that won't need rebuilding
  • Integrations that handle failure gracefully
  • Code another developer can pick up
  • Clear decisions made early
  • Boring reliability maintained throughout
  • and a risk flagged during scoping, not during launch

Good software is mostly a matter of clear decisions made early and boring reliability maintained throughout. We'd rather tell you a simpler approach will work than build something impressive that costs more to maintain — and we'd rather flag a risk while it's still cheap to change.

We'd rather be useful than impressive.

that has cost us a few projects

A wall-mounted grid of empty card slots in a dim studio, lit by raking light

Where we're based and who we serve

Most of our clients are within a short drive of the studio

Our base is in Singapore and most of our clients are here too: founders building a first product, established SMEs modernising a manual process, and larger organisations adding a new layer to existing systems. Working locally has practical advantages — we understand the business context, we can meet in person when it helps, and we're in the same time zone as the teams we work with.

We also take on projects from elsewhere in Southeast Asia and beyond. The delivery process is the same; only the meetings are remote. What changes is the amount of context we have to build up front, so we plan a little more time for that at the start.

The people you'll work with

You'll deal with the people doing the work, not an account manager relaying messages. On most projects that's a small team, and we keep it stable through the build.

Whoever leads the build

One person owns your project from scoping through launch. They know why every decision was made, because they made it or were in the room when it happened.

The specialists the work needs

Mobile, back end, integration, interface — we bring in the people whose discipline the project actually calls for, and keep them on it.

A stable team through the build

Swapping people mid-project costs time and context, so we don't do it as a matter of course. The handover you get at the end is the same team you started with.

An honest answer about skills

If your project needs something we don't have in-house, we'll say so and bring in someone who does, rather than stretch and learn on your budget.

ask us before you sign

How we communicate

Projects go wrong when communication goes quiet. Here's what you can expect from us during a build, and what we ask of you in return.

What you can expect from Null Lines during a project, and what we ask of you
During the project From us From you
Progress Regular updates and working software you can open and try A named person who can make decisions
Bad news Told when we know — a delay, a constraint, a decision that needs input Feedback within a few days, not a few weeks
Technical choices Explained in plain language, with the trade-off stated The question you actually want answered
Status reports Short and specific — what moved, what's blocked, what's next Ten minutes to read it and reply
Handover Documented and walked through with whoever takes it on Access to the accounts that own the work

You shouldn't need a computer science degree to understand what you're paying for. When something changes, you hear about it when we know, not at the deadline — and if you'd rather see the process laid out step by step, the delivery page covers each stage in order.

See how we work

What we won't claim

We won't tell you we're the best studio in Singapore, because that's not a claim anyone can verify and it isn't useful to you. We won't promise a project will be flawless or that nothing will ever need fixing.

What we will do is give you an honest view of the scope, the trade-offs and the risks, and then do the work properly. If a project isn't a good fit for us, we'll say so early — which saves us both time and, more often than not, saves you a retainer.

  • We won't Say a build will be flawless, or that nothing will ever need fixing
  • We won't Take a project we don't have the people for
  • We won't Quietly change the scope and send the bill later
  • We will Tell you early if your project isn't a good fit for us

the first meeting is the cheapest place to hear it

How we think about the market

Singapore's development market is crowded, with large agencies, boutique studios and freelance developers all competing for the same work. The differences that matter to a buyer aren't usually visible on a homepage.

What matters is whether a team can handle both the front end and the back end, whether they've dealt with integration constraints before, and whether they communicate clearly when things change. Those are the questions we'd ask any studio, including ourselves, and they're the ones we've positioned Null Lines around rather than around a slogan.

In practice that means we'll ask about your existing systems before we talk about features, we'll tell you which parts of the build are routine and which are genuinely uncertain, and we'll be specific about what we're not going to do. If you're comparing studios, those three answers will separate the field faster than any portfolio page.

Questions worth asking us

  • Who writes the code, and have they built anything like this before?
  • What happens when an integration fails at 2am?
  • What would you tell us not to build?
  • Who picks this up if we stop working with you?

Before you get in touch

The things people usually ask us first. If your question isn't here, ask it directly — there's no sales script.

Do you only work with clients in Singapore?
No. Singapore is our base and most of our clients are here, but we take on projects from elsewhere in Southeast Asia and further afield. The delivery process is the same; the meetings are remote, and we spend a little more time building context at the start.
Can you take over a project another team started?
Often, yes — but we'll want to read the code before quoting. Handover projects range from straightforward to genuinely difficult, and the honest answer usually comes out of a day or two of looking rather than a conversation. We'd rather spend that time before you commit.
Do you build native mobile apps or cross-platform?
Both, and the choice depends on what your app has to do. If it leans on camera, background location or device hardware, native usually earns its cost. If it's mostly forms, lists and API calls, a cross-platform build gets you to both stores with one codebase. We'll recommend the one that fits, not the one we prefer.
Who owns the code when the project ends?
You do. We work on your accounts and your repositories, and the handover is documented so another team can continue without us. That's the arrangement we'd want if the roles were reversed.

Tell us what you're building.

If you want to know whether we're a fit for your project, the fastest way is a short conversation. Tell us what you're trying to build and what constraints you're working within, and we'll give you a straight answer about how we'd approach it. There's no sales script and no obligation.

The studio

the kettle is on if you're nearby