Skip to content
KIVA

About

I like problems.Especially the hard ones.

Sometimes I think in complicated ways so other people don't have to.

I'm Nurkiva, Kiva for short, and I founded KIVA. I build websites, business applications and automations. Honestly, though, it isn't the coding that drives me but the problem behind it: the spreadsheet nobody trusts, the task that takes five steps where one should do, the system that works but nobody enjoys using.

My mind is rarely happy with the first answer. I want to know why something works the way it does, who is allowed to change what, and what happens when two people act at the same time. Not because I like complicated solutions, but because a truly simple solution usually takes a lot of thinking. The complexity belongs in my work, not in your day.

I learned much of what I know because a real problem needed a working solution. Today I design and build websites for small businesses in the Philippines and Brazil, including 40 shop redesigns that are now live. And for an international platform client I build systems teams use every day, such as the tool that replaced a payment team's 28 spreadsheets. Those case studies are confidential and available on request.

Team

Who you work with

KIVA is a small team of three. I plan and build every project myself, from the Philippines. Gabby and Citha work from Indonesia and make sure you always know who to ask.

How I think

Messy business in. Working system out.

First understand the mess, then find the connections, then remove the steps nobody needs. Try it.

Today

  • 01SpreadsheetsScattered lists nobody reconciles
  • 02MessagesImportant details buried in chats
  • 03Manual tasksThe same steps every day
  • 04Separate toolsNo shared workflow
  1. ProblemWhat costs time or nerves today?
  2. RulesWhat may happen, and what never?
  3. StateOne source everyone trusts.
  4. ActionThe next step happens on its own.
  5. ResultLess work left over.

Field notes

What you can expect from me

Ask before I build
I keep asking until I understand the real problem, even if that seems slower at first.
Rules belong on the server
What must never happen should be impossible in the system, not just forbidden.
Show early
A clickable preview in week one is worth more than a perfect spec in week four.
Simple over clever
I choose the simplest technology that does the job, and document it for the next person.
Honest scope
Fixed prices where the work is clear, transparent estimates where it isn't, and no invented promises.
Knowing when it's done
I like to keep improving. So we agree up front what "done" means, and you get a solution, not an endless project.

Honest about the limits

  • KIVA is a small team of three. I plan and build every project myself, so we only take on a limited number of projects at once.
  • We work in English. By email and WhatsApp we write to you in German or French if you prefer, with the help of translation tools; calls are in English.
  • If I see a simpler way or think a requirement isn't needed, I'll say so. And if a project needs other specialists, I'll say that too.

I'm not looking for easy problems, but for ones worth solving.

You don't need a finished specification. Tell me what isn't working, what takes too much time, or what you'd like to change.

Start a project →