Pricing

The whole product. One plan price.

Choose the project capacity your team needs. Every plan connects planning, field records and commercial work.

Choose your project capacity.

Plus

Keep a focused set of projects, daily work and costs in one place.

₹15,000per month

Annual ₹1,50,000: two months free

4 active projects

No seat cost. Unlimited people.

One-time onboarding and data import assistance: ₹60,000

Start the free trial

Pro

Coordinate a growing portfolio, with room to add projects as you win them.

₹28,000per month

Annual ₹2,80,000: two months free

12 active projects

Three times the projects of Plus for under twice the price.

No seat cost. Unlimited people.

One-time onboarding and data import assistance: ₹1,12,000

Start the free trial

Enterprise

Bring multiple entities into an agreed commercial arrangement, with onboarding.

From ₹65,000per month

Invoiced annually, on agreed terms

Unlimited active projects

No seat cost. Unlimited people.

Onboarding and data import assistance: in the agreed terms

Book a demo

Prices in INR. Cancel any time. Every plan starts as a 7-day trial and the trial asks for no card. Annual is payable by bank transfer against a proforma invoice.

No seat cost, on any plan. You pay for projects running at once, never for people.

Completed and cancelled projects free a slot. Monthly Plus and Pro billing is by card; Enterprise is invoiced on agreed terms.

Onboarding and data import assistance is charged once, when your first paid plan starts, and is the same on monthly and annual billing. It covers setting up your company, importing your projects and training your team.

Need room for more projects?

Add 3 more active projects for ₹5,000 a month, or 8 more for ₹10,000 a month, on Plus or Pro. Add-ons can be taken or dropped at any renewal.

Feature switches are administrator choices. They do not change the plan price.

Read the subscription terms

What is in every plan.

Not a summary of the product: the product. Every group below is in every plan, at every price, and none of it is sold separately.

Some of this ships switched off and an administrator turns it on. Field attendance always does: it records where a named person is standing and photographs their face while it does so, and a company arrives at that deliberately, having drawn its own site boundary and told its crew what is being recorded. Switching a module on or off never moves the price.

Field attendance availability must be confirmed before rollout. The module starts switched off.

The plan and the schedule

Work plan and critical path: A work breakdown with owners and dependencies, a Gantt beside it, and the critical path computed across four dependency types with float on every task.
Baselines and variance: Freeze the approved plan and measure everything after it against that, so the schedule shows where each task was originally meant to be.
Task board: The same tasks as cards in status columns, for the people who work from a board rather than from a schedule.
Risk and contingency register: Probability against impact, a response strategy on each risk, and the time and the money held in reserve for it.
Weekly project review: A structured pass over one project: what moved, what slipped, what is due next, and what is blocked.
Your existing plans, imported: The programme you already keep in Excel comes in, with every problem flagged before a single row is written.

The yield and the asset

Yield assessment: All 8,760 hours of a year walked sun position by sun position, returning P50, P90 and P99 with an uncertainty budget that names every term it carries and marks which are measured and which are assumed.
Three satellite datasets, cross-checked: PVGIS, NASA POWER and NSRDB fetched live for the exact coordinates of the site, never bundled and stale, with the disagreement between them measured and printed rather than assumed away.
The manufacturers’ own component files: Reads the .PAN and .OND files suppliers actually ship, fingerprints the exact bytes, and keeps them, so every forecast can name the file that made it.
Asset model and long-term economics: NPV, IRR, payback and levelised cost for an asset you build and then operate, with month-by-month output tracked against the contracted standard.
Tariff calculator: Arithmetic on figures you type, for sizing a tariff before there is a project to hang it on.

The bill of quantities, and the bill drawn from it

Bill of quantities: The BOQ as the spine of the contract: item, unit, quantity and rate, with progress measured against it rather than estimated over it.
Running-account bills: RA bills built from measured quantities item by item, through draft, submitted, approved and paid, never typed in a second time.
Billing position: What you have earned against what you have billed, from measured progress, with a one-click draft bill for the unbilled balance.
Variation orders: Priced changes to the agreed scope, approved on their own and added to the revised contract value.
Retention: The money the client holds back from each bill, carried on the job until acceptance releases it.
Advances and their recovery: A mobilisation advance recorded once and recovered pro rata across the bills that follow it.
The invoice as a document: A printable invoice carrying a schedule of what is being billed, drawn from the BOQ or the RA bill where those exist, on your own letterhead.
Credit notes: An issued invoice is frozen in the database, so a correction is a credit note against it and what was billed never changes shape.
Quotations: A priced offer built from the sourcing list, a margin set on every line, exported as a branded PDF.
Sourcing list: What things cost you, kept in the background, so pricing a job is looking a rate up instead of remembering it.

Tax, as statute writes it

GST, output and input: Charged on the full value of the supply, split inter-state or intra-state as the place of supply decides, with input credit tracked against it. Retention and recoveries are deductions from the payment, never from the taxable value.
TDS, both directions: What a client withholds from you and what you withhold from a vendor, with the statutory section, the challan and the return quarter kept beside each entry.
The rate that applied, kept: Every rate is stored on the transaction as it stood that day, so a bill raised last year still explains itself this year and is never re-derived from a rate that has since changed.

Receivables, and the cash behind them

The invoice register: Four questions answered in one place: what is outstanding, what of that is overdue, what is being retained, and what is parked waiting on a second signature.
Ageing and MIS: Receivables and payables bucketed by how overdue they are, across every project including the ones another company has shared into your account.
Cash schedule: The dated list of money you expect to receive and to pay out, which is also where the agreed cost of the job comes from.
Payment reminders: A daily nudge for what is coming due, switchable on its own, because wanting the schedule is not the same as wanting to be emailed about it.
Working capital: What the job has locked up: receivables, retention held, advances outstanding, and the funding gap those three add up to.
Cash flow stress test: The same schedule run three ways: optimistic, a base case at thirty days late, and a stressed case at sixty days with a dispute in it.
Earned value: Planned value, earned value and actual cost captured as snapshots, with the SPI and CPI they give and the S-curve they draw.
Billable flow: The deal on one sheet: the client’s price, every intermediary’s royalty, your billable value and margin, and the subcontract underneath it.
Work orders: What you have ordered from vendors and subcontractors, with the committed value carried against the project before any invoice arrives.
Multi-currency: A cost or an invoice recorded in the currency it was actually transacted in, at the rate that applied then, and reported in your base currency.

The site, day by day

Daily progress reports: Manpower, work done, weather, delays and the equipment log, filed from site and tied to the tasks and the quantities they move.
Site photographs: The project gallery, with photographs attached to the work they prove rather than dropped in a folder.
Field attendance: Photo attendance measured against the site’s own boundary plus a distance you set, not a circle drawn round a pin. Each capture keeps the position, the accuracy the phone itself claimed, and the server’s time rather than the phone’s.
The muster, read as a register: Who marked in, organisation-wide: project by project and person by person, without opening a project to find it. A supervisor sees the crew, a site engineer sees their own record, and the scope you were given is printed on the page.
No score, and no automatic decision: Attendance never scores a person and never refuses one. Anything unusual is written on the record in plain words, the signals collapse to two of them, clear or review, and a named supervisor makes the call. A wage decision made by arithmetic is not one anybody can cross-examine.
Materials: Orders, delivery confirmation and installation status, carried per project.
Drawings register: Revisions and issue status held in order, so the site is never working off a superseded sheet.
Project documents: Contracts, correspondence and certificates: everything that is not a drawing or a photograph.

Approvals, and the record

Change approvals: A change to money above your own threshold parks as a request until a finance manager or a project head approves it, with remarks, and with delegation when an approver is away.
The append-only record: Every governed change lands in a log that only grows. Nothing in it can be edited or deleted, by anyone, including us. Corrections are new rows.
The issued bill, frozen: Issuing a bill stamps the tax point and locks its figures and its wording in the database itself, where even our own keys cannot rewrite them.
Roles, enforced below the application: Twenty-three roles with tenant isolation in the database, so a site engineer never sees a rupee figure and it is the database that refuses, not the screen.
Compliance register: Insurances, statutory licences and registrations tracked to their expiry dates, with alerts at 90, 30, 15 and 7 days.
Bank guarantee register: Every guarantee with its purpose, its bank and its expiry, alerted on the same 90, 30, 15 and 7 day ladder.
Terms that explain themselves: A question mark beside every technical label opens a plain-words explanation where the term stands, because the people reading these screens are engineers and accountants, not software people.

Partners, and the client

Subcontract work packages: Packages, their values and the back-to-back payment cascade, managed by your own team.
Subcontractor portal: Subcontractor staff sign in and see their own packages and nothing else. Letting an outside company into your account is a security decision, so it is a switch of its own.
Vendor master: The approved supplier list, with what each one has delivered carried on it.
Client portal: A token-gated progress view for your client, with no account for them to create. The link is view only: it shows progress and takes nothing back.
Client workspace: The client, or the authority above them, signs in to their own account and finds every project shared with their organisation in one place. You invite them by their email address, they accept signed in, a question is asked under the asker’s own name, and all of it is fenced by the scope set on the share.
Client document vault: The LOA, the agreement and the letters that belong to a specific client, filed against that client and read signed in, never through the public link.
Cross-company project sharing: Invite another company that has its own account into one project, with an explicit scope: schedule, tasks, photographs, financials, and whether they may share it onward.
Project discussion: One thread per project, visible to everyone with access to it, the partner companies included.

Getting your data back out

Reports and exports: PDF and Excel for the financials, the daily reports and the portfolio summary.
API keys: Issue a key and let your other software read and write directly.
Outbound webhooks: Invoice raised, phase changed, task completed: pushed to a URL you control as they happen.

See your work in Norvis.

Bring a project and the questions your team needs to answer.

Request demo Start the free trial