About

The vendor I'd want to hire.

Nate spent years on the buyer's side as a software engineer and project manager, doing the testing vendors skipped and writing the documents they didn't. Keel North is built on what made projects work.

Fig. 01 · Founder

Portrait of Pinaet Poonsarakhun, founder of Keel North
NamePinaet Poonsarakhun (Nate)
RoleFounder and lead engineer
BasedThailand
Works inThai · English
LinkedIn profile ↗

Sheet 01

The buyer's seat

For years, Nate sat on the buyer's side of the table. The team built and ran software that real users depended on every day. There were never enough people to build it all, so it hired vendors: nine of them, on nine projects, while Nate developed nine more in-house.

Three of those vendors failed. Work arrived untested, so the team became the testers while users found the bugs. The team wrote the vendors' documents. Once, a vendor's security mistake became Nate's to answer for.

What worked was just as clear: projects the team built and launched first, bringing vendors in only to scale, and the vendor project where the senior engineer at the pitch was the person who built the system. Keel North is that vendor.

AI projects now fail the way vendor projects always have: the demo works, real data breaks it, and nobody can say what it achieved. Most Thai organisations already use AI; few have it in daily work. Keel North builds AI the way it builds everything else: on your own systems and data, measured before and after, and safe enough for your IT and data protection teams to approve. On the financial platform, the AI assistant already answers from the platform's own help content, shows its sources, and hands over to a person when it isn't sure.

Eighteen hull drawings on a red waterline. Hired out: 9 vendor projects, 6 completed and afloat, 3 failed and capsized below the line. Built in-house: 9 projects, 7 went live and afloat, 2 never launched. HIRED OUT · 9 VENDORS 6 COMPLETED 3 FAILED BUILT IN-HOUSE · 9 PROJECTS 7 WENT LIVE 2 NEVER LAUNCHED WL
Fig. 02 · 18 projects from the buyer's sideAbove the line: completed or live. Below it: failed or never launched.

Sheet 02

What went wrong, and what we do instead

  1. On the buyer's side: Work arrived untested, and users found the bugs.

    At Keel North: You review the work. You don't test it.

  2. On the buyer's side: The team wrote the vendor's documents.

    At Keel North: We write the requirements, design and handover documents.

  3. On the buyer's side: A stalled project went to a new vendor who wanted to start again.

    At Keel North: Code and accounts are in your name from day one, with a handover pack anyone can pick up.

  4. On the buyer's side: The senior at the pitch was not the person who built it.

    At Keel North: The engineer you meet is the engineer who builds it.

Sheet 03

The work behind it

The work Nate is proudest of is a financial platform for a US company, founded and still led hands-on, with a security review before every release. Over 15 years Nate has also built a payment gateway for an international school on KBank and ttb that has processed about 600 million baht, and staff and recruitment portals for 12 schools across Asia.

600MTHB through a payment gateway on KBank and ttb
12schools on staff and recruitment portals
18projects from the buyer's side
15years building software

At a glance

Proudest work
Founder of a US financial platform, still leading its build hands-on
Payments
A payment gateway for an international school on KBank and ttb, about 600M THB processed (≈ US$18M)
Scale
Staff and recruitment portals for 12 schools across Asia
Buyer's side
Software engineer and project manager: 9 vendors managed, 9 projects built in-house
Education
MSc in software systems engineering
Teaching
University IT lecturer, two years

Sheet 04

How we work

We are

  • Plan first, then a fixed quote
  • Security-grade by default
  • Bilingual, Thai and English
  • Specialists in LINE connected to real backends

We are not

  • The cheapest quote on the market
  • A body shop renting out developers
  • An agency with account managers between you and the work
  • A “magic” AI shop promising everything in a week
Three dock berths. Two hold a hull each, labelled Build 01 and Build 02. The third is empty and dashed: the next build waits its turn. BUILD 01 BUILD 02 waits its turn NEXT IN LINE
Fig. 03 · Two berths

So every project gets full attention, we take on at most two builds at a time.

Your code lives in your own repository from day one, and every handover comes with documentation, so your team is never locked in.

Start with a Blueprint.

Two to three weeks, a fixed build quote at the end, and every document is yours whether or not we build together.

Book a Blueprint →