How it worksOne loopFive steps

How it works.

One loop, run every cycle: plan, work, ask the experts, update the world, re-plan. People make the calls. The system carries everything between them.

The world is the project’s shared record: every fact, answer and decision, with who it came from and when.

The loop, one row per step
StepWhat happensWhoThe world gets
01Plan the workTeamPLAN ADDED IN EVERY AREA
02Work sessionOne personDRAFTED WORK ATTACHED TO THE PLAN
03Contact expertsPerson approves, system sendsOUTREACH SENT · WAITING ON ANSWERS
04World updatesOutside expertsANSWERS IN · AREAS CONNECTED
05Re-plan and notifySystem, then teamPLAN REVISED · TEAM NOTIFIED

Try it · Nothing is sent

Plan a project

Pick an example. The draft builds in place: phases, then sections, then the work, then the experts it would contact, each with a drafted one-line ask.

Pick an example

Worked examples of how the system structures pre-development: phases, then sections, then the work with an owner on each item, then the experts it would contact. Nothing is sent. Your own project’s plan is drafted with you, from its real site and program.

Draft plan · Pre-development · Worked example

No project chosen yet

Waiting for a project

  1. 01Phases
  2. 02Sections
  3. 03The work, with an owner on each item
  4. 04The experts it would contact, each with a drafted ask

01 Plan the work

Every project starts as a tree.

Phases, then sections, then the work. Every item has an owner and a status, so the system can read the plan and everyone can see it.

You approve the plan before anything runs, and again whenever the system proposes a change to it.

Plan · ExampleApproved by the team before anything runs
  • ProjectExample: 40-unit mixed-use building
  • PhaseSite and zoning
  • SectionZoning
  • WorkMap use, height, density and parkingSystem
  • WorkConfirm what needs reliefExpert
  • WorkDecide whether to seek itPerson
  • SectionSite control
  • WorkList every easement on the titleSystem
  • PhaseFeasibility
  • PhaseCost and capital

02 Work session

Thirty to forty minutes, one person, with the AI.

Each person works their part of the plan in a short session. The AI brings what changed since last time, the drafts waiting on a decision, and the messages waiting on approval.

They decide. It records the decision in the world and carries the rest until the next session.

Work sessionOne person, 30 to 40 minutes
  1. What changedAnswers that came in and what they moved.
  2. Decide on draftsMemos, asks and estimate lines waiting on a call.
  3. Approve outreachFirst messages to new experts, under whose name.
  4. Set what’s nextWhat the system works on before the next session.
  5. Done. The system carries it from here.

03 Contact experts

The system asks. A person approves the first message.

The system finds the experts a project needs and drafts each ask. A person approves the first message to any new expert, and decides whose name it goes out under.

After that, the system sends follow-ups on time and chases until the answer comes back.

Expert outreachOne approval, then the system carries it
  1. 01SystemFinds the expert the work needsFrom the plan: who has to answer this, and what to ask.
  2. 02SystemDrafts the askOne clear question, with the context an expert needs to answer it.
  3. 03Approval · PersonApproves the first messageA person approves the first message to any new expert, and whose name it goes out under.
  4. 04SystemSends, then chasesFollow-ups go out on time until the answer comes back.
  5. 05WorldRecords the answerAs given, with who said it and when.

04 World updates

One living model of the project.

The world holds every fact, answer, decision and open question, with who said it, when, and what it changed. It is what the system plans from.

It gets denser as the work happens. The next project starts with the method, never your numbers, names or terms.

Almost emptyA new project: the areas of work, and little else.
Mid-projectPlan, work and the first expert answers, linked.
DenseMany cycles in. Older knowledge rests in gray.

05 Re-plan and notify

When an answer changes the plan, the plan changes.

Work moves up, new work appears, and some work is no longer needed. The system proposes the new plan and the team confirms it.

Each person gets one message with what’s theirs now. Nobody hunts through a thread.

Re-plan · ExampleAfter counsel answers: no relief needed
  • Map use, height, density and parkingUnchanged
  • Prepare a variance applicationremoved
  • Confirm the as-of-right massing with the architectadded
  • Open lender conversationsMoves up: the program is settledmoved

Notified · one message per person

Development lead Two items are yours now: the massing check and the lender conversations.

06 What we don’t automate

Some things stay with people, by design.

The system carries the work between decisions. The decisions, the signatures and the relationships stay yours.

  • Judgment callsWhich site, which risk, which answer is good enough. The system lays out the options. A person decides.
  • SignaturesThe system signs nothing. Contracts, applications and approvals go to the person whose name is on them.
  • MoneyThe system never moves money or commits spend. It drafts the request; a person approves it.
  • RelationshipsLenders, partners, neighbors, the planning board. The system prepares you. You have the conversation.
  • Professional stampsLicensed professionals keep responsible charge of their work. The system seals nothing.

07 Your data

Your project stays your project.

The system learns how projects get done. It does not take your numbers, your names or your terms to anyone else’s project.

Before a pilot starts we put the details in writing: where your data is hosted, which model providers process it and on what terms, who at Nupixl can see it, how you export it, and how it is deleted.

Stays in your project

  • Your numbers and deal terms
  • Drawings, documents and correspondence
  • The names of your people, partners and experts
  • Every answer and decision on your project

What carries forward

  • How the work was planned and in what order
  • Which questions needed asking, and which kind of expert answered them
  • How long each kind of work took
  • Never your numbers, your names or your terms

08 Architecture

Three parts.

Short enough to fit on a page. The walkthrough goes as deep as you want.

  1. 01PlanA tree of the project’s work, with an owner and a status on every item.
  2. 02WorldThe project’s record of facts, answers and decisions, each with its source and date.
  3. 03LoopThe software that drafts, sends, chases and re-plans, and stops for a person at every approval.

See the system run on a real project.

We walk your team through the plan, the world and the loop as they run on a real project, and answer the questions your IT and legal teams will ask.

Request an architecture walkthrough