Investor + candidate briefing — May 2026 · v0.1

One platform
where 1
used to be.

Nodii is a modular operating platform for distributed service businesses, starting with ISPs. Each module can stand alone. When modules are used together, they share identity, events, permissions, and workflow context. Five modules are built; first anchor ISP onboarding begins this week.

Briefed by Abhi Sathya · founder
Document nodii / investor + candidate deck / v0.1 — 2026‑05‑04
01 — Context
The problem

These businesses coordinate
too much work by hand.

Internet providers. Cable operators. Regional logistics. Equipment-as-a-service. Multi-brand distribution. Customers, partner networks, field teams, billing, provisioning, support, and infrastructure all affect each other. Most operators manage that with several disconnected tools and a lot of manual follow-up.

Investor + Candidate Briefing02 / 15
01 — Context
The product model

Modular alone.
More useful together.

Standalone adoption

A customer can adopt Finance, HR, Provisioning, Inventory, Shipping, or Customer & Service without replacing everything at once.

Customer & Service Finance HR Provisioning Inventory Shipping
Connected platform

When modules are connected, they share customer identity, employee identity, permissions, events, service state, billing context, and operational history.

Identity Events Permissions Operational state
Adopt one module. Get more value from every module added.
Investor + Candidate Briefing03 / 15
Current state

Initial product built.
First real deployment starting.

05
Modules built
Customer/Service, Finance, HR, My Tools, and Provisioning.
01
Anchor ISP onboarding
First deployment cycle begins the week of May 4, 2026.
Pre
Revenue stage
Commercial validation starts with this deployment.
180
Days to learn
Prove one operational loop and repeatable onboarding.
Bengaluru — in-person hybrid · investor + candidate briefing
02 — Product
What is built now

Each module needs standalone value.
Connected value is the point of the platform.

Built
Customer
& Service
Standalone: customer lifecycle, onboarding, services, support, distributors, promotions, and credits.
Connected: customer and service context for Finance, Provisioning, Support, and field workflows.
Built
Finance
Standalone: receivables, payables, payment collection, reconciliation, and Zoho Books sync.
Connected: uses customer, service, distributor, and collection context to reduce finance/operations mismatch.
Built
Provisioning
Standalone: ISP service activation and FreeRADIUS sync.
Connected: turns plan, billing, and customer lifecycle state into network access decisions.
Built
Human
Resources
Standalone: employee sync, onboarding, announcements, policies, attendance, and leave workflows.
Connected: ties employee responsibility to field work, approvals, support, and audit trails.
Built
My Tools
Standalone: employee switchboard, tasks, metrics, and self-service surfaces.
Connected: gives employees one place to act on work coming from other modules.
Future surfaces
Inventory
& Shipping
Standalone: stock, equipment, fulfillment, and shipping workflows.
Connected: can block or unblock service activation based on equipment and delivery state.
Investor + Candidate Briefing05 / 15
02 — Product
How adoption starts

Integrate first.
Replace only where it makes sense.

Keep existing systems
Do not go back to the studs.
Operators can keep Zoho Books, GreytHR, KYC/compliance providers, payment gateways, helpdesk tools, or legacy workflows while Nodii enters where change is practical.
Add Nodii modules
Improve one workflow at a time.
Customer lifecycle, finance, provisioning, HR, inventory, shipping, or support can run independently where the operator needs a better workflow.
Connect the context
Native and external data both matter.
Connected modules and external providers feed shared identity, events, permissions, workflow state, and audit history. This is the base for future automation.
KYC / identity GSTIN Zoho Books GreytHR Payments NAS / RADIUS Helpdesk
Investor + Candidate Briefing06 / 15
02 — Product
Platform model

Nodii is not one app.
It is a modular operating layer.

External providers
KYCGSTINZohoGreytHRPaymentsNAS/RADIUSHelpdesk
↓
Integration layer
ConnectorsSync jobsProvider eventsImport/export
↓
Shared identity Events Permissions Audit log Operational state
↓
Nodii modules
Customer & ServiceFinanceHRProvisioningInventoryShippingMy Tools
↓
Cross-module workflows now; scoped agents later
Modules create adoption. Shared context creates compounding value. Integrations preserve existing workflows.
Investor + Candidate Briefing07 / 15
Why ISPs first

ISPs put the whole
problem in one place.

ISPs concentrate customer management, field operations, billing, provisioning, collections, and partner networks into one painful workflow. They are a useful first market because customer state and service state have to match for the business to work.

Section II — Where we're starting
03 — Wedge
First workflow to prove

Customer state becomes
service state.

01Customer onboarded
02KYC / compliance captured
03Area, distributor, and field team assigned
04Plan selected
05Service activated
06Provisioning sync triggered
07Billing, collections, and support use the same state

This is where fragmented tools hurt most. Customer, finance, provisioning, support, distributor ownership, and field execution all need the same state. If this loop works, the rest of the operator becomes easier to expand into.

Investor + Candidate Briefing09 / 15
04 — Proof plan
What we are proving in the first deployment

Commercial validation has not started yet.
This deployment is the test.

Hypothesis
Proof target
Operators will adopt Nodii module by module.
Anchor starts with selected workflows, not forced full replacement.
Modules can stand alone.
Each adopted module creates value independently before the full platform is in place.
Connected modules compound.
Customer, service, finance, provisioning, and support context reduce duplicate work.
Integrations reduce migration friction.
Existing Zoho, GreytHR, compliance, payment, or provider workflows remain usable.
The same architecture can repeat.
A second deployment should require configuration, integrations, and templates, not a rebuild.
Agents will have useful context later.
Core events and external provider data become visible through one permissioned operating context.
Investor + Candidate Briefing10 / 15
04 — Expansion
Expansion thesis

Same modules.
Different operator shapes.

01
Direct adjacencies
Cable operators, regional ISPs in other states, and satellite or IoT operators. Similar customer, service, provisioning, and distributor patterns.
02
Operations twins
Logistics aggregators, equipment-as-a-service, and multi-brand distribution. Similar customer, field, partner, finance, and inventory patterns.
03
Broader operators
Businesses where a holding company or operator runs many teams, locations, partners, or tenants on one operations stack.

Expansion should mean adapting modules, integrations, permissions, and workflow templates. It should not mean rebuilding Nodii for each industry. Direct adjacencies have to prove that before the later stages matter.

Investor + Candidate Briefing11 / 15
04 — Future interface
From shared context to scoped action

The agentic layer only works
if the operating context exists first.

Native Nodii modules
External integrations
Shared identity / events / permissions
Telemetry and audit trails
Scoped agents that can investigate, recommend, and later act

Agents are useful when they can see customer state, billing state, provisioning state, employee responsibility, tickets, approvals, and external provider data in one permissioned context.

Unpaid customer → billing state visible → provisioning action suggested.
KYC incomplete → onboarding blocked → field team notified.
Provisioning failure → NAS context and ticket context visible together.
Distributor margin mismatch → finance and customer ownership joined.
Investor + Candidate Briefing12 / 15
05 — Team
What joining now means

The product is real.
The system is still being shaped.

The work is modular SaaS infrastructure: multi-tenant services, provider integrations, permissions, and cross-module workflows. The first customer is real and deploying. The architecture is still being shaped. Early engineers will define the standards the platform scales on.
Systemsmulti-tenant services, workflow orchestration, provider integrations, permissions, and audit trails.
DomainRADIUS/provisioning, finance-grade state, employee responsibility, and operator-specific workflows.
Contextagent-ready operational data, but only after the core workflows and integrations are reliable.
TeamBengaluru, in-person hybrid, with visible impact on real operators.
Investor + Candidate Briefing13 / 15
05 — Posture
Risks / disconfirming signals

The main ways
this could fail.

R/01
Modularity has to stay real
If modules cannot stand alone cleanly, Nodii becomes a bundled implementation project. If they do not compound when connected, Nodii becomes just another suite.
R/02
Repeatability may not appear
If the anchor deployment requires too much custom work, the architecture is not yet repeatable.
R/03
Provisioning reliability is required
If service state cannot reliably drive access control, the first ISP workflow does not hold.
R/04
Integrations can become hidden services work
Connectors need product boundaries. Otherwise adoption gets easier but implementation becomes hard to repeat.
R/05
Second-customer validation matters
One anchor proves the problem is real enough to start. A second operator tests whether the playbook travels.
R/06
Hiring density is part of the bet
This needs engineers who can handle infrastructure, product judgment, customer ambiguity, and operator details.
Investor + Candidate Briefing14 / 15
The ask

We are entering
the first proof window.

Investors
Track the next two quarters with us: first operational loop, modular adoption, connected-module value, and repeatable onboarding.
Candidates
Join before the architecture hardens if this kind of product and infrastructure work is your kind of hard problem.
Email abhisathya4@gmail.com
Question we are testing Can modular adoption become one shared operating layer?
First call 30 minutes — investor or candidate track.
Current stage Early.