← All work
BiiosSaaS2026

The ERP we run our own company on

Nexus ERP puts tasks, CRM, invoicing, chat and an encrypted credential vault in one workspace, scoped per organisation. We built it, we run Biios on it, and the careers page on this site reads its openings straight out of it.

The Nexus ERP workspace: a sidebar of Dashboard, Tasks, CRM, Chat, Banking, Files and Vault beside a My Tasks list with status and assignee against each row.

The brief

Most companies we work with run on the same pile. A task board, a spreadsheet of invoices, a chat app, a shared document of passwords nobody wants to talk about, and somebody whose real job is keeping the four in step. We had that pile too. Nexus ERP is what we built to put it down, and it is the system Biios runs on now.

What was actually wrong

An ERP is easy to start and hard to finish, because the difficulty is never the features. It is that each one has to know about the others. An invoice belongs to a project, a project has tasks, tasks belong to people, people hold roles, and the role decides who may see the invoice at all. Get that wrong and you have four apps in a trench coat. It also has to be multi-tenant from the first commit, since one organisation's data should never be one missing filter away from another's.

The thing itself

The Nexus ERP interface, captured from the product’s own site. From ₹149 per seat per month, after a 14-day trial.

  • The Nexus ERP CRM: a leads list with qualification badges, an invoice total, and counters for total leads, qualified leads and amount invoiced.

    Leads carry a status and a call log, then become clients, quotes and invoices without leaving the workspace.

  • Nexus ERP chat: a team channel with member avatars, a task discussion marked In Review, and a channel list with unread counts.

    Team, project and task channels, so a discussion sits against the thing it is about rather than in another app.

  • Nexus ERP banking: bank and cash accounts in rupees and dollars with a combined balance, and a list of recent transactions.

    Bank and cash accounts across currencies, with balances derived from payments in and expenses out.

  • Tasks that carry a workflow

    Assign, submit, review. Recurring tasks and workflows spawn on a schedule, and the ETA engine widens deadlines around working hours and each team's holiday list.

  • A pipeline that ends in an invoice

    Leads with a calling queue and call log, then clients, projects, quotes and invoices with line items, tax, discounts and instalments.

  • Chat where the work is

    Team, project and task channels over WebSockets with a polling fallback, so context sits next to the task rather than in a separate tool.

  • One ledger for the money

    Multi-currency bank and cash accounts, expense tracking with receipts, and a finance overview whose numbers come from the records underneath.

  • Credentials, properly encrypted

    AES-256-GCM per organisation with TOTP, time-limited sharing and linked passwords, so the shared document of passwords can finally be deleted.

  • A door for your clients

    A separate customer portal on its own domain with its own accounts, so a client sees what concerns them without a seat in your workspace.

How we worked

  1. 01

    Modelled the permissions before the features

    Sixty-five permission flags packed into a single BigInt, five locked system roles and unlimited custom ones. Settling that first meant every module was built against one gate instead of each growing its own.

  2. 02

    Made the organisation the boundary

    Workspace, CRM, finance, chat and vault are all scoped to an org. White-labelling falls out of that: a customer gets their own name, logo, colours and custom domain, with TLS issued automatically.

  3. 03

    Derived the money rather than typing it

    Bank and cash accounts across currencies, with balances computed from linked invoice payments in and expenses out. Quotes convert into invoices, and recurring quotes generate their own drafts on a schedule.

  4. 04

    Ran our own company on it first

    Biios uses Nexus for tasks, clients and hiring. The careers page on this site is not a copy of a job board: it reads openings live from the ERP through its API. That is a blunt test, and it is why the rough edges get found by people who can fix them.

What changed

Nexus is in early access at nexuserp.dev on per-seat pricing, with a fourteen-day trial that does not ask for a card. What matters more to us is that it is not a demo. Our tasks, our clients, our invoices and our hiring all live in it, which is a harder commitment than any roadmap.

One
Workspace for tasks, CRM, chat, finance and credentials
65
Permission flags, so people see exactly their own remit
Live
Runs Biios daily, including the careers page on this site

Got a version of this problem?

Tell us where you are and where you want to be. A paragraph is plenty to start, and you will hear back within a business day.

Start a project

Have a project in mind?
Let’s build something extraordinary.

Tell us where you’re headed. We’ll bring the team to get you there.