Services for businesses in Lucknow, India and beyond
Business systems that make status visible: portals, CRMs, internal tools and document control.
Business systems are the software a company runs on: portals for customers and partners, CRMs shaped around the real sales or service process, internal tools for the team, and document control for files that need an owner, a version and an approval. They exist so status is visible and hand-offs do not depend on memory.
Sunbeam designs and builds these systems from Lucknow for teams across India and for clients in the Gulf, the UK and the US. When a product you already pay for fits the workflow, we configure it. A custom system earns its place when the workflow is hard to represent in that product, or when the current tools have become a second job.
The business case
What better looks like.
- One status a customer and the team can both trust
- Follow-up that has an owner
- Files with a current version and a named approver
What it is
Portals, CRMs, internal tools and document control
These four shapes share a record: a customer, a matter, a job or a file, and several people who need a reliable view of it. A portal shows the customer the same status the team sees. A CRM shows the next action on a relationship. An internal tool answers the questions managers ask on Monday. Document control keeps the file from forking into conflicting copies. They are often one product with several doors. The record comes first, then the screen each role needs.
Document control here means who may upload, which version is current, who must approve, and how long the file is kept. It implements the controls you and your advisers specify. It is not a certification, and it does not replace counsel or an auditor. Asking questions of the content is a different job, covered under knowledge systems.
Portals
A customer, client or partner signs in to see progress, send a request or collect a document, so the team spends less of the week answering status questions.
CRMs
Relationships and the next step. If a known CRM already matches the pipeline, we configure it. A custom CRM is for a process that product cannot represent without permanent workarounds.
Internal tools
Queues, assignments, exceptions and the few numbers that change what someone does today. Deliberately smaller than an enterprise suite.
Document control
Check-in, current version, owner, approval and a record of important changes. Useful when a stale file circulating as final is a real risk.
Who it is for
Operators who feel the cost of unclear status
This fits service firms, clinics, agencies, manufacturers, property and education teams, and any company whose work is a pipeline of cases. The symptom is a client asking for an update while three people check three places, or a lead that is "with someone" and nobody can say who. The sponsor needs authority to decide the statuses. A system that encodes a process the team will not follow becomes shelfware, so discovery follows the process people actually use, including the shortcuts.
Customers are chasing updates
A portal is worth considering when status requests are a measurable part of the week.
Follow-up depends on memory
A CRM or a lighter lead workflow fits when opportunities cool down because nobody owned the next call.
Managers rebuild the same report
An internal tool fits when the same spreadsheet is assembled by hand for every meeting.
Files have no current version
Document control fits when the wrong draft reaching a client is a real risk.
How we work
Model the record, then the smallest set of screens
We walk a handful of real cases from first contact to closed. That shows the statuses, the documents, the people, and the systems that must remain the source of money, identity or clinical records. The first release covers one role's worst hour. A staff queue with an honest status is more useful than a portal, a CRM and a document store that are all half-finished. You own the code and the data unless we agree otherwise in writing.
Which record is the centre?
A client, a job, a property, a student, a shipment. Later screens hang off that choice, so we make it explicit.
What are the real statuses?
The few states that change who acts next, and the rule for moving between them.
What stays outside?
Accounting, payroll or an industry platform often stays. We integrate at the boundary instead of recreating it.
Who tries it first?
A pilot group on live work, with a short guide. A wide launch onto a team that still has the old spreadsheet open rarely sticks.
Typical stack
Postgres holds the record. Next.js is how people reach it.
Business systems are usually Next.js for the screens, Postgres for the records, Go for imports and integrations, and AWS for hosting, files and backups. Postgres matters here because statuses, permissions and "who changed this" need constraints. Files live in object storage. The database stores the owner, the version and the link. If HubSpot, Zoho, Odoo or a similar product already covers the pipeline, the work may be configuration and a small integration. Building a second CRM beside one the team must still update is a failure we try to prevent.
Interface
Next.js
Role-based screens for staff and, when the release includes it, a portal. Queues, forms and document lists are the core interface.
Services
Go
Imports from the old spreadsheet, scheduled syncs and webhooks to the tools you keep.
Records
Postgres
Cases, relationships, permissions and the audit of important changes, documented so a later report is a query.
Operations
AWS
The application, private file storage and backups in an account your company owns. Access and environments are part of handover.
Timeline ranges
One shape first, then the doors that depend on it
Ranges assume the statuses are agreed and someone can review a slice every week or two. Document migration is the usual surprise: unnamed files, duplicates, and versions nobody will claim. We import a clean current set and leave the archive for a later decision, rather than pretending a decade of folders will become tidy on its own.
2 to 4 weeks
Discovery
A map of the record, the roles, the first release, and a recommendation that may still be to configure the tool you have.
6 to 12 weeks
An internal tool or document checklist
One team, one queue or one controlled folder workflow, including the import of the current working set.
8 to 16 weeks
A portal or a CRM-shaped system
Staff workflow plus a customer or pipeline view, reminders, and one integration.
A further slice
The next door
A customer portal on a trustworthy staff system, or reporting on a CRM, scoped after the first release is in use.
Process
From interviews to daily use
Adoption is part of the process. A pilot group uses the system on real work before the whole company is asked to switch.
01
Walk real cases
A few recent jobs, including one that went badly. The failures show the fields the happy path forgets.
02
Name the record and the roles
We write the model in plain language and confirm who can view, edit and approve.
03
Cut the first release
One primary screen, the statuses it depends on, and an explicit list of later work.
04
Build and import
The working set comes in with a sample you can check. A bad import is not hidden behind a new interface.
05
Pilot with one group
A small team uses it on live work. We fix the friction that would stop a wider rollout.
06
Hand over and widen
Documentation, access, and a decision about the next slice: a portal, reminders or reporting.
Who this is for
For teams ready to improve an important part of the business.
- Service and operations teams chasing status
- Companies outgrowing a generic CRM
- Firms that need a current version of important files
Frequently asked questions
Useful questions before you begin.
Should we build a CRM or configure one we can buy?
We map the pipeline first. Configuration is the better start when a known product can represent the stages and the hand-offs. Custom work is for a process that would otherwise live in permanent workarounds.
Can a portal and an internal tool share one system?
Yes. The usual shape is one record, a staff queue, and a customer door added once that status is trustworthy.
Will document control make us compliant?
It can implement the controls your advisers specify: versions, owners, approvals and retention. Conclusions about compliance belong with those advisers.
Can you migrate our spreadsheets and files?
We import the current working set and check a sample with you. Bringing a full historical archive across is a separate decision.
Related capabilities
One connected engineering team.
Custom software development
Custom software development for businesses in Lucknow, across India, and in the Gulf, the UK and the US. Systems built around the workflow you already run.
Custom CRM development
Custom CRM development for businesses that need a customer system shaped around their sales, service and operations workflows.
Internal tools development
Internal tools development for dashboards, operations portals and systems that help teams make faster, better-informed decisions.
Considering whether a custom approach is justified? Read our build-versus-buy decision guides, explore industry workflows, or review how ownership and handover work.
Start with the business problem, not the technology.
Tell us what is getting in the way. We will help identify a useful next step.