Case study · CRM, ERP-lite, and operations automation
Victus Global — CRM / ERP-lite Operations System
Designing lifecycle logic, approvals, role-based visibility, automation, and handoffs around the way the business actually operated.
Systems Designer · Automation and AI Workflow Lead
- DeliveredDelivered operations system
- Sanitized reconstructionPublic case study
01 · At a glance
What this system enabled
- Business need
- Designing lifecycle logic, approvals, role-based visibility, automation, and handoffs around the way the business actually operated.
- Nelcys’s role
- Systems Designer · Automation and AI Workflow Lead
- What was delivered
- CRM, ERP-lite, and operations automation
- Core systems
- Notion · n8n · Notion AI · Google Workspace
Maturity and public status
- DeliveredDelivered operations system
- Sanitized reconstructionPublic case study
02 · Business need
What the business needed
The business needed connected operational logic across intake, approvals, client and project creation, customer success, follow-ups, role-based work, and procedures.
The value was not the novelty of a no-code platform. It was the lifecycle design, governance, visibility, and adoption model built around the business.
03 · What needed to change
The operating risks to resolve
Connected business-development intake, approvals, project creation, delivery, and customer-success handoff in one governed operating model.
Records, approvals, projects, client context, and follow-ups were difficult to connect.
Different roles needed useful views without duplicating the underlying truth.
Lifecycle transitions and customer-success handoffs depended on memory and manual coordination.
Automations needed to preserve approvals and operating ownership.
04 · What I delivered
My role in the system
I owned the business outcome, operating logic, system boundaries, acceptance criteria, delivery direction, validation, and final acceptance. AI-assisted development and specialist collaboration supported implementation where the context required them.
- Designed the CRM and ERP-lite data and lifecycle model.
- Mapped intake, approval, project creation, client creation, and customer-success handoffs.
- Created role-based dashboards and follow-up workflows.
- Directed n8n and Google Workspace connections, including Google Sheets where operating inputs required it.
- Built the operational handbook, SOP structure, and governance rules.
- Used Notion AI for structured support without changing approval, record-ownership, or handoff rules.
05 · How it works
How the system works
Approved intake creates linked client and project records in the operating system. Role-based views expose the same underlying truth to the right people, while automation supports follow-up and customer-success handoffs under documented governance.
Selected system
Intake and approval
Captures requests, required context, decision owners, and approval evidence.
Boundary: Records do not progress into committed work without the required decision.
Systems in context
- Notion
- CRM, ERP-lite records, work views, SOPs, and governance
- n8n
- Approved lifecycle automation and handoffs
- Notion AI
- Structured drafting, summaries, and repeatable operational support inside the governed workspace
- Google Workspace
- Google Sheets, documents, communication, and operating inputs
06 · How I think
The decisions behind the system
Tools change. The durable work is deciding what owns truth, what may move, what must stop, and what evidence is enough.
Design the lifecycle before the databaseMap decisions, owners, states, and handoffs before creating records and views.
- Why
- A flexible tool can reproduce operational confusion just as easily as it can resolve it.
Use one record, many role viewsCreate role-based dashboards from shared underlying entities.
- Why
- Teams need different working views, not competing versions of the same client or project.
Gate record creation through approvalsCreate downstream client and project structures only after the relevant decision is captured.
- Why
- Premature creation introduces clutter, false commitments, and unclear ownership.
Pair automation with an operating handbookDocument what each automation does, its owner, its exception path, and the manual fallback.
- Why
- Operational adoption depends on knowing how the system behaves when the normal path breaks.
07 · How it was delivered
From model to working system
- Mapped the operating lifecycle and translated it into linked Notion entities.
- Built role-specific dashboards from shared records.
- Connected approved intake to client, project, customer-success, and follow-up workflows.
- Directed n8n and Google Workspace integrations, including Google Sheets inputs, around defined approvals and handoffs.
- Applied Notion AI to structured operational drafting and summaries while keeping approvals and source records under named ownership.
- Created SOP and operational-handbook structures for adoption and exception handling.
Guardrails
Where the system must stop
- Approval precedes downstream record creation where required.
- Role views do not duplicate the underlying truth.
- Automations retain a named owner and manual fallback.
- Public framing emphasizes business logic and governance, not no-code novelty.
08 · What changed
What changed
- Connected intake, approvals, client and project creation, customer-success handoff, and follow-up in one operating model.
- Created useful role-based visibility without duplicating core records.
- Made lifecycle rules and exceptions easier to operate through SOPs and governance.
- Turned flexible tools into a structured business system rather than a collection of disconnected databases.
09 · Public evidence
What the public record can show
Evidence is described conservatively. Any visual proof added to this page must be redacted, captioned, and checked before publication.
Diagram
Lifecycle architecture
Shows decision gates, record creation, role views, handoffs, and exception paths.
Sanitized evidence
Role-view reconstruction
A sanitized example of how shared records support distinct operating responsibilities.
Narrative record
Governance narrative
Explains the relationship between automations, approvals, SOPs, ownership, and fallback behavior.
10 · What this proves