Nupik Wenpach LLC · Independent software studio

Obsessive about the parts you will never even notice.

Which is exactly the point. A week of work scrapped on a Thursday. The same screen rebuilt four times. A Sunday spent on something nobody will click. Two hours on one word. Custom sites, web apps, and native iOS, built end to end and still looked after once they ship.

See what is live Start a project

01 / Work

What is live right now

Three with a public address. One built for my own use, two built for people who sell food to their own town. The rest is under someone else’s name and stays there.

The Desk in modulate.pro, Work side: a strip of notes needing attention, a timeline of the day’s deadlines, and three columns of notes headed Today, Ahead and Unscheduled, with a composer resting across the bottom.
The same desk with the composer open and a single hash typed, which has opened the account’s tag list, each tag with its own colour dot.
The ops dashboard: numbered work orders with their priority, trade and location, a project card tracking a tank battery repaint against its budget, and a rail of counts, hours and the month’s spend by cost code.
Web Closed beta

modulate.pro

Catch the thought before it is gone. A note written in the truck is waiting on the desk: Today, Ahead, and the ones nobody has dated yet, with the day’s deadlines laid out above them. Work on one side and life on the other, so the half you are not in stays out of the way. Offline is not a failure state.

On the org side the same notes become field operations: work orders carrying a trade and a priority, projects tracking spend against budget, and a board showing what has nobody on it. Which is how a note about a leaking pumpjack turns into a job with a number.

  • Next.js
  • React
  • Railway
Request an invite
A bakery’s own storefront during an open drop: four pastries with prices, an almost-gone chip on each as the pool nears its cap, a countdown to close, and the pickup day.
The maker’s pickup-day board: nine orders across four columns headed To review, Confirmed, Ready and Picked up, each card carrying the buyer, the order and the one button that advances it.
The bake sheet for one drop, headed thirty-four items across ten orders, every product grouped by pool with its own total, beside tabs for the label sheets it prints.
Web Live

OvenBoard

Sell your bread the way you bake it. A shop for independent bakers who work in weekly drops: the ordering window opens on its own, the caps hold, and the regulars get first look. Nobody promises the same last loaf to two people in two different messages again.

Pickup day it turns into a board. Orders move from new to ready to handed over, the bake sheet prints itself with the labels, and the whole thing comes back out as a spreadsheet whenever it is asked for. Every shop gets an address of its own.

  • Next.js
  • React
  • Postgres
  • Stripe
  • Railway
ovenboard.com
A farm stand’s storefront with preorders open: pantry goods with prices, an almost-gone chip on each as the pool nears its cap, a countdown to the ordering deadline, and the market pickup day.
The grower’s stall board for a Saturday market: ten orders across four columns headed To review, Confirmed, Ready and Picked up, with a pool line showing boxes already past their cap.
The production sheet for one preorder, headed twenty-six items across ten orders, everything to pick and pack grouped by pool with totals, beside tabs for the label sheets it prints.
Web Live

GrazePost

The same argument pointed at market day. Farm stands and market sellers take preorders through a shop of their own, so the last jar is spoken for once instead of twice, and the people who turn up every Saturday get the first pick they have earned.

Saturday morning it is a board at the stall: what is packed, what is paid, what is still to hand over. Pack sheets and labels come off it, and standing orders mean the regulars stop having to ask.

  • Next.js
  • React
  • Postgres
  • Stripe
  • Railway
grazepost.com

02 / Process

There is a process. It’s just not that interesting.

Price up front. A link in week one. Nobody disappears after launch. What matters is the part in between, where ideas get said out loud before they are ready and taken seriously even when they sound wrong. The best one wins, and whose it was does not come into it.

  • Marketing sites and storefronts
  • Web apps with accounts, data, and payments
  • Native iOS, through App Store review
  • Internal tools and integrations

03 / Why a person does this

Software gets opened by people who are tired, in a hurry, and already annoyed about something else entirely.

Noticing where it makes that worse takes somebody who also gets annoyed.

There is no instrument for it. Nothing in a test suite catches a screen that is technically correct and quietly cold, or an error message that manages to blame the person reading it, or an empty state written as though nobody would ever arrive at one. Those get found by someone running roughly the same nervous system as the person who will open the thing, with a low tolerance for the feeling of something being not quite right.

Mine is unusually low. It is why the edges line up, and why the eight pixels nobody will consciously see still got moved. Less a service on offer than a condition worked around, by going and fixing whatever set it off.

AI is part of how this gets built, the same as it is for everyone now, and anyone telling you otherwise is either lying or losing. It is not the part you are paying for. It has never opened something at the end of a long day and been let down by it.

Every project built as if it were my own. One of the three above actually is.

04 / Contact

Tell me about it

A site, an app, or a half‑formed idea you cannot quite describe yet. I read and answer everything myself, usually inside a day.

noah@nupikwenpach.com