FIELDCRAFT · NPM · MIT
One schema, every surface
Forms, validation, conditional logic and multi-step flows resolved from the same JSON — web, mobile shell, or server render.
fieldcraft.squaredr.tech ↗ACCEPTING WORK · 2 SLOTS THIS QUARTER
Software that survives contact with production.
I build React and TypeScript products for founders. A human owns the architecture and signs off on every line — AI just does the typing. That is the part that makes it hold up.
schema.json → <FormEngine />● live
[{
"text", "Name"
},{
"email", "Email"
},{
"select", "Role"
},{
"submit", "Send"
}]
Name*
Email*
Role
Select...
Send
44
FIELD TYPES
1,095
TESTS
100%
TYPESCRIPT
MIT
LICENCE
44FIELD TYPES
1,095TESTS PASSING
100%TYPESCRIPT
3PAYMENT PROVIDERS
MITLICENSED
0RUNTIME LOCK-IN
REACT 19NEXT.JS
01 / START HERE
Tell me which of these is true today.
Three situations cover almost everyone who writes to me. Pick the one that stings and I will take you straight to the engagement that fits.
BUILD
Nothing exists yet
- You have a spec, a Figma, or just conviction
- You need something users can actually touch
- You need to start taking payments
- The deadline is this quarter, not next year
TYPICALLY
from $1,800
FIX
It exists and it hurts
- Pages are slow and nobody knows why
- A rewrite keeps getting proposed
- One integration is quietly losing money
TYPICALLY
$1,200 flat
PARTNER
You need someone senior, not a hire
- Shipping stalls between contractors
- You are hiring or raising and need a counterpart
- The roadmap needs an owner who writes code
TYPICALLY
from $2,800/mo
02 / EVIDENCE
I am my own hardest client.
No logos to show you yet — so instead, two packages I built for myself, in the open, with public tests. Same discipline you would be buying.
ARCHITECTURE
Layers, not lock-in
Swap any layer. Keep the rest.
PAYKIT · NPM · MIT
One line changes provider
Stripe, Razorpay and PayPal behind a single adapter interface. Your keys stay on your server.
striperazorpaypaypal
CHECKOUT.TSX
const pay = createCheckout({
provider: 'stripe',
})INSTALL
Running in five minutes
No account, no dashboard, no vendor keys in my hands.
npm i @squaredr/fieldcraft-react
+ 0 peer conflicts
import { FormEngineRenderer }
✓ pass it a schema — done
03 / METHOD
Twice the speed. None of the shortcuts.
A human owns the architecture, the edge cases and the review. AI does the typing. Everything that leaves here has been read by someone who will answer for it — and that someone is me.
- 01Day 1
Scope
A 30-minute call. We agree what ships, what does not, and what "done" looks like. You get a written spec within 24 hours.
- 02Day 2–14
Sprint
AI-assisted development, human-reviewed commits. Daily async updates. You see real code on real infrastructure, not mockups.
- 03Day 15
Ship
Staging review, edge-case sweep, performance pass. Once you sign off it goes live and I hand over the keys.
- 04Ongoing
Support
Thirty days of bug fixes included. After that, retainer or ad-hoc — your call. Documentation and handover are part of every engagement.
// ACCEPTING WORK · 2 SLOTS THIS QUARTER
Got something that needs building?
First reply inside 24 hours. Discovery call is free, 30 minutes, no deck.