From hand-cut joinery to AI-native software
Ikena Design & Build started in Alaska timber-frame and Honolulu finish carpentry. Today it ships software. The standard didn't change — the substrate did. Here's the through-line, and why a contractor's instincts make a good operator-engineer.
Most software studios start with engineers who eventually learn the trades they serve. Ikena Design & Build started the other way around. The operator spent a decade swinging hammers — Alaskan timber-frame, Alyeska Resort, Chugach Powder Guides snowcats, and a long Honolulu run in specialty flooring and finish carpentry — before writing his first production line of TypeScript.
That isn’t a quirky biography. It’s the thesis of the studio.
The standard is the same
Joinery, done well, is uncompromising. A mortise either holds or it doesn’t. Trim is square or it announces itself for thirty years. A floor that wasn’t acclimated cups, and no amount of marketing changes that. The standard for finish carpentry is binary: it passes the test of a fingertip dragged along the seam, or it fails it.
Software, done well, has the same property. A query either returns in 8ms or someone notices. A multi-tenant boundary is either bulletproof or someone reads another tenant’s data. An iOS scan either captures the wall or it doesn’t, and no amount of “shipped fast, will iterate” rhetoric makes a broken scan useful on a jobsite. The standard is the same standard. The substrate is just different.
The trades teach a person to respect the boundary between good enough to pass inspection and good enough to live with for thirty years. Most software people have never had to live with their own work the way a finish carpenter does. The owner of the house comes back in five years and runs a hand along the casing. If your software ages like cheap pine — fine for a quarter, sad after a year — that’s a kind of failure most engineers never internalize, because they’re working on something they’ll never see again.
What the trades teach about scope
A renovation contract has a number on it. You quote the work, you scope it tight, you build to the scope, and you change-order anything that wasn’t in the original drawings. The clients who hire Ikena for renovations didn’t sign up for surprises. The clients who hire Ikena to build software shouldn’t either.
The software industry’s love of “agile scope” — meaning, in practice, we’ll figure out what we’re building as we go — is a luxury the trades don’t get. A contractor who finds termite damage doesn’t pretend it’s part of the original quote. He stops, documents it, sends a change order, gets it signed, then resumes. That’s not bureaucracy; that’s how you stay in business and respect your client’s wallet at the same time.
Discovery — the paid engagement that precedes the build — exists for the same reason a contractor walks the site before quoting the renovation. You don’t know what you’re committing to until you’ve measured. Ikena charges $5,000 to $15,000 for that walk-through, and applies it to the build if the client moves forward. The math is the same math a finish carpenter does on a site visit. The output is just a product spec instead of a punch list.
What the trades teach about ownership
Every house Ikena finished was a house Ikena had to drive past for years afterward. You see your work. You walk inside it on the next job. You hear, second-hand, what the owners said to a guest about the trim. Every project becomes part of your portfolio whether you wanted it to or not.
That posture transfers. The studio doesn’t write disposable software. We don’t ship a Polycam wrapper that we know is fragile and call it MVP. We don’t bolt no-code tools together and hope they don’t get acquired. The default is to build natively — own the data layer, own the auth layer, own the deploy. Because in three years, someone will run a finger along the seam, and you want the seam to still be tight.
What the trades teach about pace
A renovation takes the time it takes. You can’t pour concrete faster than concrete cures. You can’t acclimate hardwood in 48 hours when it needs two weeks. You can hire more bodies and you can stack trades, but past a certain point you’re just rushing a fixed-duration job and producing the kind of work that calls itself out in the first hot summer.
Software has the same constraint and pretends it doesn’t. There is a fixed minimum time to build a multi-tenant SaaS with billing, auth, an admin panel, and a customer-facing portal. You can pay $300K for a “senior team” to build it in eight weeks — and you’ll get eight weeks of work, with eight weeks of corners cut. Or you can pay one operator to build it in twelve weeks and get something that doesn’t embarrass you on the demo.
Ikena ships engagements in six to twelve weeks. Two builds at a time. Not because we’re slow. Because we’re matching the work to the time it actually takes, the way a contractor matches a remodel to the calendar it actually needs.
The pivot
We don’t do construction anymore. The 2026 pivot moved Ikena Design & Build from a design-build renovation practice to a software studio. The brand carried because design and build was always a verb, not a category. We design and build. The substrate now is web products, AI-native systems, multi-tenant SaaS, iOS native apps. The customers are still mostly Hawaii businesses, plus a growing set of mainland and remote engagements where Hawaii expertise is a genuine moat (property data, contractor workflows, GET tax for SaaS, that kind of thing).
What didn’t pivot:
- Discovery is still paid before the build. We learned this from the trades and we’re not unlearning it.
- Two engagements at a time. Care doesn’t scale.
- One operator on every project. You work with the person responsible for every decision.
- Owned stack, end to end. We don’t rent infrastructure we can build.
- Mālama on the work. Kuleana on the relationship. Laulima with the partners we bring in.
Why we think the trades-to-tech direction is rare and good
Most of the software people building software for trades have never been in a trade. Most of the contractors trying to digitize themselves end up adopting whatever SaaS their competitors use, which is whatever SaaS got VC funding in 2019. There’s a vanishingly small overlap — people who’ve actually poured concrete, paid Hawaii GET, written a change order with shaking hands, and can ship production TypeScript.
That overlap is the moat. Not the code. The standard. The operator who knows what it costs to do work right, who has explained a $5K addendum to a homeowner across a kitchen table, who has had to live with their own seams — that operator is rare on both sides of the fence. And the work that operator produces is the work that has a chance of being good in five years.
That’s the studio. Welcome.
Ikena Design & Build is a software studio in Honolulu, Hawaiʻi. We design and build AI-native web products for the trades, real estate, and the people who keep everything moving. Begin a design engagement.
Building Hawaii Insurability Brief: A Free Property Hazard Lookup for Hawaii Homeowners
A builder's account of why we built a free 10-field hazard lookup for Hawaii properties — lava zone, FEMA flood, tsunami, coastline distance, hurricane wind, wildfire risk, BFE, shoreline management area, roof age, and carrier availability — and how the freemium model works.
Building AI-native products on Claude: a Honolulu studio's playbook
Six products live, all built against the Anthropic Claude API. Here's how we structure AI calls in production, what we cache and what we don't, how we keep latency under 2 seconds for user-facing flows, and the patterns that have actually shipped — not the hype.
Hawaii GET tax on SaaS subscriptions: a practical guide
Hawaii taxes SaaS revenue differently than most US states — and very few founders know the rules until their first G-45 return is overdue. Here's how Hawaii's General Excise Tax actually works for subscription software businesses, with the rates, the forms, and the traps.