Most company websites make it hard to tell working software apart from a picture of working software. This page draws that line for Aivance Technologies, Inc. in plain terms, so that nobody has to guess.
It is written for anyone assessing us — a reviewer, a partner, a first customer — and it is deliberately unflattering where the truth is unflattering.
01Why this page exists
Every product you can click on this website is a demonstration. It runs inside your browser tab, it uses invented sample data, and it saves nothing anywhere. Each demonstration says so on its own screen. The one thing on this site that is not a demonstration is the enquiry form behind the pricing buttons, which opens your own email application and sends us nothing until you press send there.
Separately from those demonstrations, there is a real server application under active development. The two are not the same thing, and this page describes each of them honestly.
The short version. The Trevano ERP server application is real and under active development. The three products you can click on this site are browser demonstrations of the interface, not connections to that server. Nobody is paying us yet.
02Trevano ERP — running software
Trevano ERP is a multi-tenant business system: one installation serving many separate companies, with each company’s records held apart from every other company’s. It is the product we intend to sell first, and it is where nearly all engineering effort has gone.
The list below counts feature areas inside one running application, not products and not marketing headings. It is long because a business system that does not cover the whole of a small firm’s day is a system that firm still has to work around. Anyone who thinks the list is longer than one person could build should ask for the walkthrough in Section 9 and watch it open in front of them, unfinished parts included.
2.1 Modules that exist in the server application
Named as a business would name them. What each one does is not set out here: a reader assessing whether this exists needs the names and the walkthrough in Section 9, not a specification.
Inventory · Sales and purchase · Invoicing · Accounts and expenses · Customers · Human resources · Payroll · Attendance · Leave management · Roles and permissions · Multi-branch control · Live location tracking · Delivery rider tracking · Production management · Orders and delivery · Barcode and QR scanning · Low-stock alerts · Commission tracking · Document storage · SMS and WhatsApp messaging · E-commerce and Facebook order intake · Multi-currency · Data export
That is twenty-three names. Several of them carry further modules inside the server that are not listed separately here, and the true count is above thirty-eight. We publish the twenty-three rather than the thirty-eight because a name can be checked against a running system and a number cannot. Anyone who wants the longer figure tested should ask for the walkthrough in Section 9. The thirty-eight includes the nine AI modules, which are named in 2.2 below along with a plain statement of what is and is not connected.
On the two tracking modules, and on staff. Location tracking of employees, and the same tracking applied to delivery riders, is the part of this list that deserves a question, so it is answered here rather than waited for. A business using Trevano decides whether to switch it on and who it covers. That business is the data controller for what it collects, and telling its own staff and holding a lawful basis for watching them are its obligations, which we do not take on for it and do not pretend to have discharged. On our side of the line there is a limit we will not cross: no AI module in this product scores, ranks or makes decisions about a person’s work. The EU AI Act classes that use as high-risk, and we will not ship it until we can meet everything that classification asks for.
On the outside connections. The SMS, WhatsApp and Facebook modules are written and wired, but each one reaches the outside world through a platform that grants access on its own terms. Meta approves WhatsApp Business and Facebook order access; that approval is a launch step, and it is not in hand yet.
2.2 The AI modules
Nine of them are built and sit inside the product: the assistant, sales prediction, inventory forecasting, expense analysis, cash-flow prediction, fraud detection, customer segmentation, smart reports and document reading.
One thing about them has to be said plainly, and the same sentence appears on the home page. The models behind these modules are not connected yet. The modules exist, the places they plug into exist, and the wiring to the models is the work that follows. Until that is done we will not describe any of them as live, and the assistant in the browser demonstration answers only by counting rows that are already on the screen.
2.3 Security and compliance work already completed
These are finished pieces of work, not intentions:
- A catalogue of every database column that holds personal data. Regulators require a breach to be reported accurately and quickly. Without knowing exactly which columns hold personal information, no such report can be honest. This catalogue was completed and merged on 23 August 2026.
- A guard against that catalogue drifting out of date. If a future change adds a column holding personal data and does not record it, the build fails rather than passing quietly.
- Written security drills. The procedures for handling an incident exist on paper before they are needed, rather than being improvised during one.
2.4 Work in progress right now
- Two-factor authentication for administrator accounts. The accounts that can see across companies are the ones worth attacking, so they are the ones being hardened first.
- A health endpoint. A single address that reports whether the system is actually working, so that an outage is detected by us rather than reported by a customer.
- Account recovery. A safe route back in for someone locked out, which is a security surface in its own right and is being treated as one.
Design for this work is approved and the code is being written. It is not finished, and this page will say so until it is.
03How it is built and tested
- Separation by company is enforced in the database schema, not merely checked in application code. One company cannot read another’s rows even if the application above is wrong.
- An automated test suite runs on every change. A change that breaks something else does not reach the main branch.
- Every change goes through review before merging. Work is described, reviewed, tested and then merged — not written straight into the live system.
- Each piece of work is scoped in advance and is not allowed to quietly redesign anything it was not asked to touch.
On how it is written. Aivance is a one-person company. The engineering runs on a written process: each change is specified before any code exists, built with AI coding tools working to that specification, checked by an automated test suite, and reviewed against the specification before it is merged. Nothing reaches the main branch that has not been through all four steps. The specification, the tests and the review are the founder’s own work, as are the architecture decisions the code is written against; the tools carry the typing, not the judgement. Nothing has been contracted out to anyone, and the software Aivance ships is its own. We state this plainly because the process is the reason the work holds together, not something to be discovered later.
04The three demonstrations on this site
The Trevano, Zocia and Meherya pages on this website are self-contained demonstrations. Each one runs entirely in your browser tab. There is no server behind them, no account, and nothing is stored — closing the tab discards everything you did.
- Trevano demonstration — seven screens showing the interface and the arithmetic of the ERP: a dashboard, inventory, point of sale, invoicing, customers, settings, and an assistant that answers questions by counting the rows on screen. Seven is what the demonstration carries, not what the server application carries; 2.1 above lists that. Its numbers are invented sample figures.
- Zocia demonstration — shows the interface of a consumer social product. No part of Zocia exists as server software.
- Meherya demonstration — shows the interface of a matrimony product, including how a match score is calculated. No part of Meherya exists as server software.
Zocia and Meherya are designs we intend to build. Today they are interface demonstrations and nothing more. Anyone assessing Aivance should weigh Trevano heavily and these two lightly. Engineering time goes to Trevano and not to these two, and that is where outside funding would go as well.
05What has not been started
- Zocia has no server software. What is on this site is an interface demonstration. None of it is connected to anything, and none of it has been built as a running service.
- Meherya has no server software either. The same applies: the demonstration shows how the matching and the privacy controls are meant to work, and nothing behind it exists yet.
- Self-service signup and billing for Trevano. A business cannot yet sign up, choose a plan and pay without us being present. That is milestone four in Section 8.
- Native mobile applications. Everything we have runs in a browser. One consequence has to be named rather than left for someone to find out: a browser cannot stop an operating-system screenshot, and no website can. Blocking one outright needs a native Android build, and telling someone that one was taken needs a native iOS build. Neither has been started. Where the Meherya demonstration shows a picture that opens once and is then erased, it goes as far as a browser allows and says so on the screen, rather than implying a protection that is not there.
These are listed so that the word “product” on this website is never doing work it has not earned. Aivance has three products. Two of them are designs.
06What we do not have
Stated plainly, because a reviewer will find out anyway and would rather read it here:
- No paying customers. Nobody has bought anything from Aivance.
- No outside investment. The company is self-funded.
- No confirmed public launch date. When there is one, it will appear here.
- No employees. One person, working to the process described in Section 3.
- Indicative pricing only. The figures on the pricing section are what we expect to charge, not what anyone has paid.
- Uptime and support commitments are not yet in force, because there is no live service to commit to.
07Where this runs, and what it costs
A question we are asked more than any other, so it is answered here rather than on request.
7.1 The production plan
Trevano is a server application with a relational database. Every company’s records are separated at the database schema level, so one customer’s data cannot be read from another’s account even if the application above were wrong.
The production environment is a single application tier, a managed database with daily backups, a separate staging copy for testing changes before they go live, object storage for documents, and monitoring that tells us about an outage before a customer does. The application is packaged so that it can move between hosting providers without being rewritten.
The company is incorporated in Delaware and the work is done from Dhaka, Bangladesh.
7.2 What it costs, and who is paying it
Two different numbers get confused with each other, so they are kept apart here.
- What is being spent today: about USD 485 a month, out of the founder’s own pocket. Development tooling is the largest line, of which AI coding tools alone are roughly USD 100 a month; the rest is the domain, the accounts the company is required to hold, and the tools the work runs on. There is no revenue against any of it.
- What the founder is not being paid: a salary. It has been deferred every month since incorporation. The work has been done; the payment has not.
- What production hosting will cost once Trevano is live: under USD 100 a month at launch scale, on ordinary commercial pricing — rising as companies are added, because each one brings storage, backups and load with it.
- What this website costs: nothing. It is a set of static files.
There is no office, no staff, and nothing at all spent on reaching customers. That is not a saving we chose; it is what a company with no outside money and no revenue can afford. The honest position is that this work needs a team, not one extra person: engineering, support, sales and everything administrative are the same person today, and each of them is a full job on its own. Nobody has been hired because there has been nothing to hire with. That, and not infrastructure, is what limits how fast any of this moves, and it is the one limit money actually removes.
7.3 What outside funding would change
Two kinds of funding are being sought, and they do two different jobs. It is worth being exact about which does which, because they are not interchangeable.
- Startup cloud credits would pay for the production environment described above — application tier, managed database, daily backups, staging, object storage and monitoring — across the first twelve to eighteen months of live operation, as companies are added and the bill grows with them. That is what such credits exist for, and it is the whole of what they can pay for. They cannot pay a person.
- Cash would pay for the three things credits cannot touch. The first hire, a part-time engineer. Not the team Section 7.2 describes, but the first person of it, and the one who ends the single-person dependency this company runs on. Twelve months of the founder’s own time on the funded work, paid as a cost of that work rather than deferred month after month as it has been since incorporation. And reaching the first hundred businesses — finding them, running trials, onboarding them one at a time and collecting written feedback from each, with a budget behind the outreach to owners who have never heard of us. That is a funded line with a real monthly cost, not spare time, and nothing is being spent on it today.
Every month so far has been paid for personally. That is possible at this size. It is not possible at the next one, and pretending otherwise would not be honest.
08The twelve months ahead
These are milestones, not dates. Each one is written so that you can tell from the outside whether it has happened. This page will be updated as they are reached, including when one slips.
Where we are today. Milestone one is in progress. Nothing after it has started.
- 1 · Production hardening complete. Administrator two-factor authentication, a health endpoint and account recovery are merged. In progress.
- 2 · First live deployment. Trevano running on production infrastructure with daily backups, staging and monitoring, and one real business using it.
- 3 · First ten businesses. Ten firms using Trevano weekly, each set up personally, with written feedback collected from every one.
- 4 · Self-service signup and billing. A business can sign up, choose a plan, pay, and be running without us being present.
- 5 · First hundred businesses. One hundred firms onboarded, the first paying customers converted, and support handled without new engineering work.
- 6 · First technical hire. One part-time engineer working to the same written process, which removes the single-person dependency this company currently has.
Milestone two is reachable without funding, because hosting is the cheap part and the product is built. Milestones three to six are a different matter: they need a second person and a budget for reaching businesses, and Section 7.2 sets out why neither exists today. For those, funding is not only a question of speed.
8.1 The same twelve months, with funding and without
- Without funding. Milestone one finishes, because it is nearly done, and milestone two is reachable. After that the work narrows to what one unpaid person can carry: the same person writes the software, answers every support question, and would have to find and set up ten businesses personally, with nothing at all budgeted for reaching them. Progress does not stop. It queues.
- With funding. The first hire takes part of the engineering load, which is what frees the founder for the ten businesses in milestone three and the hundred in milestone five. Reaching those businesses becomes a funded line rather than spare time. Milestones three, four and five can then be worked on inside the same twelve months instead of waiting behind one another.
We would rather set that out than claim the difference is only speed.
09How to check any of this
Claims are worth less than the ability to test them. You can:
- Open any demonstration and try to break it. Every count shown can be checked against the table it came from.
- Read the honesty labels. Each demonstration marks its own sample data rather than presenting it as real.
- Ask us for a walkthrough of the server application. We will show it as it is on the day, including what is unfinished.
- Write to support@aivancetechnologies.com with any question this page does not answer.
If anything on this page turns out to be wrong or out of date, tell us and we will correct it here rather than quietly elsewhere.