CRM and ERP
Custom CRM and ERP development on one shared record.
A CRM is the book of people: who they are, who owns the next step, and what was promised. An ERP is the book of work: the order, the stock, the approval, the payroll input. They fail when each book invents its own customer. This page is the shared record — roles, history, and a quotation before any screen is built.
- 50+ CRM systems delivered
- 30+ HRM platforms delivered
- History is written before the build
Relationship
- Account
- North Yard
- Owner
- Sales
- Promise
- Revised quote this week
One record
Operation
- Order
- NY-1042
- Stock
- Reserved, not shipped
- Invoice
- Not filed yet
- New
- Quoted
- Won
- In the books
Which book
Open the book that matches the work
Most teams do not need both books on day one. The first meeting names which book is already failing. The other can wait. A payroll screen is not a favour added to a sales pipeline.
CRM — the relationship
Use this book when the pain is a person, a promise, or a next step that lives in someone’s head.
- A named owner for every open account
- The last promise, written, not remembered
- A stage the team already uses: new, quoted, won, lost
- A follow-up that a colleague can see
ERP — the operation
Use this book when the pain is stock, an approval, a payroll input, or an order that does not match the promise.
- An order tied to the same account as the quote
- Stock that moves only when a named role says so
- An approval with a name and a time
- Payroll inputs a person still checks before pay
The record
Six fields the quotation has to name
A screen without these fields is a brochure. Each field below is a line in the brief: who may write it, who may only read it, and what happens when it changes.
The account
One name for the customer. Not a copy in the sheet, another in the inbox, and a third in the books.
The stage
The words your team already says. We do not rename “quoted” to a vendor’s stage because a demo used that word.
The promise
The quote, the scope line, the date. A later order points at this promise. It does not invent a new price.
The goods or the job
What was reserved, shipped, or still owed. Only if the brief includes operations. A sales-only book does not grow a warehouse by accident.
The people record
Attendance, leave, and payroll inputs when HR is in scope. The studio has delivered 30+ HRM platforms. Pay itself stays a checked step, not a silent run.
The role
Who may see the pipeline, who may change a stage, who may never open payroll. Another account cannot read this one from a link.
The history
History is part of the record, not a later add-on
A stage that changes without a name is how two books drift apart. The quotation says what is kept, for how long, and who can export it. We do not migrate a history we have not seen.
Who changed it
A stage, a price line, or a stock move keeps the role and the time. “Someone updated it” is not a history.
What is kept
The promise, the order, and the note that explained a lost stage. Enough for a manager to read next quarter. Not a hidden log you cannot export.
What we will not do
We will not invent a customer list to fill a demo, call a package “ERP” because it has a report, or promise a migration before we have seen your columns.
Where it lives
Three honest places a record can live
Building is not always the answer. The first note we send may say: stay on the sheet, keep the package you pay for, or build the shared record. That note is part of the work.
-
01
Stay on the sheet
The team is small, the columns are stable, and nobody is losing a promise. We will say so. A new system would only add a login.
-
02
Keep the package
You already pay for a CRM that holds the pipeline. The brief may be a missing field, a role, or a hop into the books — not a replacement.
-
03
Build the shared record
The relationship and the operation disagree, and the package would make the team work around it. Then the record is the product. The studio has delivered 50+ CRM systems of this kind.
Indicative scope
Three briefs. The quotation is the only price.
A public rate would ignore your columns, your roles, and whether the package you already pay for should stay. These shapes help you brief. They are not a menu of licences.
One book
Relationship or people
A CRM pipeline or an HRM record, with roles and a history, tested on a set of your real accounts. Useful before a second book.
Start with one bookThe shared record
The usual brief
The relationship and one operations book on the same account. A quote and an order cannot disagree in silence. Roles and export are in the quotation.
Brief this scopeSeveral books
After the first book is live
Sales, stock, and people records that still share one account. Quoted after the first book has run on your data, not before.
Brief this scopeBefore a book is opened
Questions that change the scope if the answer changes
What is the difference between CRM and ERP?
CRM keeps the relationship: the account, the owner, the promise, the stage. ERP keeps the operation: the order, the stock, the approval, the payroll input. They should share one account. A report button does not turn a CRM into an ERP.
Do we have to replace the CRM we already pay for?
No. If it already holds the pipeline, the brief may be a field, a role, or a connection into the books. Replacement is the brief only when the package makes the team keep a second copy of the customer.
Can one person see another person’s pipeline?
Only if the role says so. The quotation names who sees all accounts, who sees their own, and who never opens payroll or stock. A link or a hidden field does not grant the other view.
Is payroll included automatically?
No. Payroll inputs are a people-record brief: attendance, leave, and the figures a person checks before pay. Paying out is not a silent step. If payroll is out of scope, it is not added because the word ERP was used.
How is this different from a web application?
A web application is the desk: whatever roles and screens the workflow needs. CRM and ERP are a specific desk — the relationship book and the operations book. If the product is not those books, the web application page is the closer brief.
Can the books be read in Arabic or Hindi?
Yes, when the brief asks. The studio is in India. The primary market is the UAE and the Gulf. The interface can be English, Arabic with right-to-left layout, and Hindi. Stages use your words, not a translated demo.
Bring the columns you already keep
A sheet, a pipeline export, or the names of the stages is enough to start. You get a written note: this book, these roles, this history — or a recommendation to keep the package, or to stay on the sheet.
