A full operating team for units of one to five people
NEXOS gives innovation labs, spinoff offices, special units, taskforces and university incubators a set of AI departments for web, content, events, research and reporting. They work in parallel. One person approves every action that leaves the unit.
Built and run at ColorME since October 2026. Set up for your unit in 30 days.
One approver and twelve departments, working at the same time
Every request takes the same path: screened, routed, done, approved, shipped. The dots are requests moving through a unit on an ordinary Tuesday.
ColorME internal data, 1 to 22 October 2026.
Who NEXOS is for
Small units with a big mandate, a sponsor to report to, and no time to hire a full team. Pick the one closest to yours.
Try it: give the unit a request
Anyone in the unit sends a request in plain words. It is checked, routed to the right department, done, and held for your approval before anything goes out.
This demo runs in your browser with example data. In a real unit the departments work on your own systems and accounts.
What it costs to run a unit this way
Compared with hiring the six roles a unit like this usually needs: web developer, software developer, writer, event planner, research analyst and project manager.
to stand up a working unit with NEXOS, against 12 to 20 weeks to hire and ramp up a six-person team.
NEXOS: ColorME built 26 departments in 30 days, October 2026. Hiring: median 39 days to fill a non-executive role (SHRM, 2026), plus 2 weeks' notice in the US or 30 to 45 days in Vietnam (Labor Code 2019, Art. 35), plus 5 to 12 weeks to reach full productivity (Gartner Peer Community poll). Roles hired in parallel.lower annual cost than staffing the same six functions with full-time hires in the US.
Staff cost: BLS May 2025 median wages for the six roles ($547,780 in total), loaded to $712k to $783k a year with benefits (BLS Employer Costs for Employee Compensation, 2026). NEXOS cost: an assumed $8k to $13k a month for operation and model usage, not a quote. Set your own figure below.NEXOS at this run cost:
Difference:
The unit's own one to five people are not counted on either side. Rigorous field studies of AI assistance measure gains on bounded tasks, for example 26% more completed tasks across 4,867 developers (Cui et al., Management Science, 2025) and 14% more resolved support cases (Brynjolfsson, Li and Raymond, QJE, 2025). They do not measure a full unit, so treat the multiple above as an estimate.
What your sponsor receives every Monday
The report is written from what the unit actually shipped and approved that week, so nobody spends Friday assembling slides.
- Written from the work logEvery item links to the change, the page or the file it refers to.
- Decisions on the recordEach approval shows who approved it, when, and how to undo it.
- Clear asks upwardWhat the unit needs from the sponsor this week: budget, access, introductions.
09:00
Summary
The pilot page went live and drew its first 212 sign-ups. Two of three concept tests are above the target conversion rate. The demo day invitation is out, with 31 of 46 guests confirmed.
Numbers
Decisions you approved
| Mon 10:18 | Publish pilot page v2 with partner logos |
| Tue 15:02 | Send demo day invitation to 46 guests |
| Thu 10:34 | Deploy signup fix for Safari users |
| Fri 11:20 | Pause concept C ads, move budget to concept A |
Needs from the sponsor
Risks
Concept B has 40 sign-ups, below the threshold. Recommend closing it at week 4 unless the committee sees a reason to continue.
Nothing leaves the unit without a person's approval
The parent organisation's brand, data and money stay protected while the unit moves at full speed.
Sending, publishing, deploying, deleting, changing real data and spending money all wait for one tap from the person responsible. A message from another department never counts as approval.
Each deploy records a restore point and runs automatic checks. If something is wrong, it goes back in seconds.
A dedicated safety department reviews requests for personal data, risky actions and prompt injection before any department starts work.
| Time | Action | Department | Approved by | Status |
|---|
For incubators: one NEXOS for every venture in the cohort
Each startup gets its own departments for web, decks and research. The program team sees every venture on one screen and gets one weekly report for leadership.
8 ventures · example data
Built and run at ColorME
ColorME, a design school in Vietnam, built the system for itself in 30 days and runs on it every day. Every screen below was made by its AI departments and serves real students.
Orchestrator, slides, video, landing pages, SEO and security.
Anyone in the company can send requests by message.
New website and new ERP take over without downtime.
500+ requests, one board, one person approving.
How we start
We do not sell a boxed product. We set NEXOS up with your unit, starting from the work that costs you the most time today.
Sprint 30
Your unit running on NEXOS within a month, measured before and after.
- Week 1: map the unit's work and approval rules
- Orchestrator plus 3 to 5 departments on your real systems
- Approvals on your phone, daily activity digest
- First weekly report delivered to your sponsor
Run
We operate and extend the system as the unit's work grows.
- New departments when the work calls for them
- Request portal for the wider team
- Safety and security departments
- Handover pack if the unit closes or changes hands
Cohort
One NEXOS for every venture, and one view for the program team.
- Starter departments for each venture
- Portfolio view and weekly cohort report
- Demo day and event departments for the program
- Onboarding for founders in each intake
| Hiring the roles | Agency per project | NEXOS | |
|---|---|---|---|
| Time to first output | Months to recruit and onboard | Days to weeks per brief | Minutes to hours per request |
| Scope | One person per function | One project at a time | Web, content, events, research, decks, reporting |
| Who can request work | Managers | Whoever writes the brief | Anyone in the unit, by message |
| Control | Meetings and email | Contract and review rounds | One-tap approval, rollback on every change |
| When people leave | Knowledge leaves with them | Knowledge stays with the agency | Knowledge stays in the unit's system |
Questions
Do we need engineers in the unit?
No. Requests are written in plain language. During Sprint 30 we connect NEXOS to your website, analytics, email and documents, and we operate the technical side afterwards.
Where does our data live, and who can see it?
Each unit runs as its own instance, connected only to the accounts you grant. The safety department screens requests for personal data, and every external action needs your approval. We agree the data rules with your IT or legal team in week 1.
What happens when the unit closes or people rotate?
The work log, decisions, documents and department instructions stay in the system. When a taskforce ends, you receive a handover pack that the next team or the parent organisation can pick up.
Can it work alongside the parent company's departments?
Yes. NEXOS handles the unit's own work at the unit's speed. Anything that must go through the parent company, such as legal review or brand approval, can be set as an approval step.
Which languages does it work in?
English and Vietnamese are in daily use at ColorME. Content and reports can be produced in the languages your unit and your sponsor use.
How is it priced?
Sprint 30 is a fixed scope with a fixed fee. After that, a monthly fee per unit, or per cohort for incubators. We quote after a 30-minute call about your unit.
See it run on a real system
A 30-minute live demo on ColorME's own NEXOS, followed by a short conversation about your unit and what it should run first.
Prefer email? Write to hello@citidev.group