Edgebox-ResearchField Residency Network
A field residency network, live in multiple regions

New systems get built where they'll actually be used.

We place small teams of builders directly inside local businesses for a fixed residency — three weeks, start to finish — to research a real operational problem and ship something the business keeps. Not a pilot that leaves when the funding does.

3 weeks · listen, build, test in place
Every outcome · signed, not self-reported
One network · every site reachable from every other
01

Most new tools never survive the visit

The technology usually isn't the problem. A consultant shows up, builds something clever, and leaves before anyone on-site actually trusts it enough to run their business on it. Meanwhile the tools that get built are one-offs — the next shop down the street starts from zero again.

Gap 01

Training without fit

General AI literacy sessions rarely touch the specific, messy workflow a real shop actually runs on.

Gap 02

Pilots that don't stay

A working demo isn't the same as a system an owner can operate alone after the team leaves.

Gap 03

No record of what worked

Success gets reported in a slide deck, not in a form anyone else can verify or build on.

02

A private workspace, built for this shop alone

The moment a resident arrives, a dedicated workspace comes online — sealed off from the business's existing systems, but with everything the team needs already inside it. If an experiment goes sideways, it rolls back to the last good version in the same breath it took to start.

0.0s
time to a working environment

rollbacks, no penalty
0
changes to the shop's own systems
03

No resident works alone

Every site quietly stays connected to every other. A fix built in one shop is one message away from a resident somewhere else — and a shared assistant sits alongside the human team the entire time, not instead of it.

04

A second pair of hands that never tires

While the human team is out in the shop talking to the owner, an AI collaborator keeps working the tools directly — reading the code so far, drafting the next version, running the checks. Scrub through one real build session, compressed:

Day 1, hour 2 — the team sketches the shop's actual order flow on paper before anyone opens an editor.
05

What gets left behind is built to be reused

Every shipped tool is packaged the same reusable way, every time — so the next residency, in the next town, isn't starting from a blank page. An inventory tracker built for a guesthouse becomes the starting point for a farm cooperative three residencies later.

Shipped, Week 3

Order & inventory board

Built with a café owner in Mandrem, adapted for a guesthouse two residencies later without a rewrite.

Reused

Booking & schedule sheet

Started as a clinic's appointment fix, now the default starting kit for any service-based shop.

06

Proof, not a testimonial

Every claimed outcome carries a signed, inspectable record — who did the work, what changed, and when — the same way a receipt proves a purchase happened. Click to open one.

07

One pilot doesn't prove much. A network does.

Zoom out, and this stops looking like a series of local favors and starts looking like infrastructure — the same private connection, the same reusable toolkit, the same signed record, running in every town at once.

0
active sites
0
tools in circulation
0
regions
08

Two ways in

A business owner and a builder need different things from us — so they get different doors, not the same form.

For the business

Host a residency

Three weeks, a small team embedded in your operation, no obligation to keep anything that doesn't earn its place. You keep what works — free.

Thanks — we've got your application. We'll follow up by email within a few days.

For the builder

Apply as a resident

Join a small field team, work alongside a real operator on a real problem, and leave with a signed record of what you actually shipped.

Thanks — we've got your application. We'll follow up by email within a few days.