Beta — open to a first group of companies
A business system that
bends to your company,
not the other way round.
Nazzam is an operating system for the work a company actually does. The fields, the forms, the pipelines, the rules and who can see what are all yours to change — in an afternoon, without a developer, and without a migration when you outgrow the simple version.
Free plan, no card. Export everything you put in, whenever you want.
An illustration of the deals board, drawn with the product’s own styles. Sample data.
Why this exists
Nobody set out to run a company across five subscriptions.
It happens one sensible decision at a time. Each tool was the right answer to one problem, and together they are the reason the owner cannot get a straight answer about the month.
- 01
Every team bought its own tool
Sales in one app, invoices in another, tasks in a third, and the customer's history split across all of them. Each purchase was reasonable on its own. The result is a company paying several subscriptions for a picture nobody can see whole.
- 02
The CRM everyone quietly stopped filling in
It asks for fields that do not apply to your business and is missing the ones that do. So people update it on Friday from memory, or not at all, and within a quarter the pipeline is fiction that gets reported as fact.
- 03
Configurable — once you hire someone to configure it
The large suites really can model your business. They also assume a partner, a discovery phase and a rollout. That is a fair trade at a thousand people and an absurd one at twenty.
- 04
The owner finds out last
Reporting means asking four people for an update and then reconciling the answers. The person accountable for the number ends up with the least direct access to it.
The approach
One system underneath, not five products in a bundle.
Most suites are separate applications that agreed to share a login. Nazzam is the opposite arrangement: one engine that holds the fields, the permissions, the history and the API, with modules built on top of it.
An illustration of the form builder. Fields marked yours were added without writing code.
- One engine underneath, not five products beside each other
- Fields, forms, permissions, audit, search, import, export and the API are a single layer. Modules sit on top of it. The CRM is the first one — anything added later inherits the whole layer the day it appears, because there is nothing else for it to be built out of.
- Configuration is data, not a deployment
- Add a field, drag it into a section, decide which roles can read it. Create, edit and detail screens change while you are looking at them. No release, no ticket, no developer, and the same builder shapes every module rather than each one having its own settings page.
- Everything is on the record
- Every change carries who made it, when, and from which address and browser. Every automation run records what fired and why. When a number looks wrong you can read what happened to it instead of arguing about it.
Built and running
What you get on the first afternoon.
Every line below is in production and checkable from a free account. Nothing here is planned, partial, or arriving next release — that list is further down, and it is separate for a reason.
A CRM that is actually finished
Companies, contacts and deals with a drag-and-drop pipeline board, list and table views, activities, a full calendar, saved filters and a dashboard you arrange yourself.
Your fields, your forms, no developer
Add fields of twenty-odd types to any module, arrange them into sections with a drag-and-drop form builder, and every create, edit and detail screen updates. Configuration is data, not a deployment.
Automations that explain themselves
Trigger on record changes, filter with AND/OR conditions, assign owners, update fields, send email. Every run is logged with what fired and why, so a rule that misbehaves can be read rather than guessed at.
Permissions down to the field
Roles you define, per-pipeline access, and read/write control on individual fields. Every write is audited with who, what changed, from which address and which browser.
Your data stays yours
Import from CSV or Excel with column mapping and duplicate detection. Export to Excel, JSON or PDF whenever you like. Deleted records go to a recycle bin, and backups are real database dumps you can restore.
Built to be connected
A documented REST API with scoped keys, signed webhooks with automatic retries, and an OpenAPI spec generated from the same validation the API itself runs on — so the documentation cannot drift from the behaviour.
In practice
Every record can explain itself.
A deal that changed value, an owner who was reassigned, a stage someone moved on a Friday afternoon — each one carries who did it, when, and from where. Automations write their reasoning down in the same place.
This is the difference between a system a manager trusts and one they keep a spreadsheet beside.
An illustration of a record’s history. Sample data.
Fit
Worth your afternoon, or worth skipping.
Built for you if
- Companies of roughly five to fifty people who have outgrown spreadsheets and shared drives
- Businesses whose process does not match the shape of off-the-shelf software — trading, contracting, agencies, clinics, distribution
- Owners and managers who want one place to look rather than four people to ask
- Teams who already know which fields they need, and are tired of being told the software does not have them
Look elsewhere if
- Companies that need a shared inbox or invoicing inside the same system today — neither is built
- Buyers who need SOC 2, single sign-on or a procurement review to sign anything
- Anyone who needs the interface in Arabic today: the layout handles right-to-left, but the translation is not done
- Teams looking for AI features — the product has none, and the roadmap is not a feature
Not built yet
The parts we have not built.
You would find this out in the first ten minutes of a trial. Ten minutes after you had already moved your data across is a worse time to find it out, for both of us.
The AI layer
The name states the intention and the architecture is designed around it — permission-bounded, attributed, never answering from data the asker could not already see. None of it is built. Nothing in the product does anything with AI today.
Shared inbox
Connecting a mailbox so conversations sit beside the deal they belong to. Designed, not started.
Invoicing and payments
Quotes and invoices generated from records, with payment links. The export engine and numbering they need already exist; the module does not.
Projects, HR, inventory, support
The module system was built so these are configuration and a UI rather than four more codebases. That is the plan, and the CRM is the only one built.
Questions worth asking us.
- What does "beta" mean here, concretely?
- The CRM and the platform under it are built and running in production, not a prototype. What is unproven is how they behave across many different companies at once, so we are opening it to a small number at a time. Expect to find rough edges and to have them fixed quickly, because there are few enough of you that we can.
- Is there any AI in it today?
- No. Nothing in the product does anything with AI right now. The architecture was designed for it — permission-bounded, attributed, never answering from records the person asking could not already open — but designed is not built, and we are not going to describe it as though it were.
- What happens to my data if I leave?
- You export it: Excel, JSON or PDF, whenever you want, at no charge and without asking us. Deleted records sit in a recycle bin before they are gone, and backups are real database dumps rather than a promise on a status page.
- Can I pay for a plan?
- Free is the only plan you can start on your own today — card payments are not connected yet. If you need the limits of Pro or Business during the beta, contact us and we will arrange it directly.
- Do I need a consultant to set it up?
- No, and if you do, that is a defect we want reported. Import a spreadsheet, add the fields your business actually uses, drag them into an order that makes sense, and you have a working system. The parts that need thought — roles, automations — are the parts that would need thought anywhere.
- Who is behind it?
- Nazzam is a product of Brand Makers Advertising, a registered company in Cairo, Egypt. It is a small team, which is why the roadmap is short and the list of what is not built is long.
Try it against your own data, not a demo.
Import a spreadsheet of your customers, add the three fields your business actually runs on, and see whether it fits the way you already work. If it does not, export it back out. The worst case is an afternoon.