# Taskco CRM — Business Overview

> One CRM platform. Five industries. Each business gets a CRM that speaks its own language, runs on its own pipeline, and follows its own playbook — without a single line of custom code.

---

## What is Taskco CRM?

Taskco CRM is a customer-relationship platform built for businesses that don't fit a one-size-fits-all sales tool. Instead of forcing your team to use generic terms like "lead" and "deal," it learns your industry's vocabulary and processes the moment you sign up.

A study-abroad agency uses it to manage **Applications** through **Counseling → Visa → Enrolled**. A real-estate firm uses the same software to manage **Enquiries** through **Site Visit → Negotiation → Closed**. Both teams open the same login screen and see a CRM that looks built just for them.

---

## Who is it for?

| You are... | You will use it for... |
|---|---|
| A study-abroad consultancy | Tracking student inquiries through to enrollment |
| A real-estate agency | Tracking property buyers through to closing |
| A pharma sales team | Managing doctor relationships and prescription orders |
| A garments exporter | Managing buyer inquiries through production and shipment |
| A general SMB sales team | Managing leads through to closed deals |

One software. Five completely different workflows. Switching between them is a setting, not a re-installation.

---

## Why this exists

Most CRMs make you bend your business to fit their terminology. Salesforce calls everything an "Opportunity." Pipedrive calls everything a "Deal." That works for a generic sales team — but a university admissions counselor doesn't sell deals. They process applications. A real-estate broker doesn't qualify leads. They schedule site visits.

Taskco CRM solves this by separating **what your business does** from **what the software calls it**. The same underlying engine powers all five industries; only the labels, stages, and automations change.

The result: your team uses CRM in the language they already speak. Onboarding is hours, not weeks.

---

## Core capabilities at a glance

| Capability | What it does |
|---|---|
| **Lead capture** | Record every inquiry with the fields your industry actually cares about — IELTS scores for education, budgets for real estate, monthly Rx volume for pharma. |
| **Pipeline tracking** | Visual stages from first contact to closed business. Different stages per industry. |
| **Kanban board** | Drag-and-drop deals across stages. See pipeline value at a glance. |
| **Contact database** | One source of truth for every person you do business with. |
| **Activity timeline** | Every note, task, email, call, and stage change recorded against a contact, lead, or deal. |
| **Auto-assignment** | New inquiries are distributed to your sales team automatically using round-robin. |
| **Workflow automation** | "When X happens, do Y." Notify managers when a deal stalls. Auto-create follow-up tasks. Generate invoices on closing. |
| **Activity reminders** | Time-based rules notify owners when leads have gone untouched too long. |
| **Multi-tenant isolation** | Your data is fully separated from every other company on the platform — own database, own users, own customizations. |
| **Role-based access** | Admins see everything. Branch managers see their branch. Salespeople see their own pipeline. |

---

## How it adapts to your business

This table shows how the same screen looks across the five industry profiles:

| What you see | General | Education | Real Estate | Pharma | Garments |
|---|---|---|---|---|---|
| Sidebar item 1 | Leads | Applications | Enquiries | Doctors | Buyers |
| Sidebar item 2 | Deals | Enrollments | Property Deals | Orders | Orders |
| Sidebar item 3 | Contacts | Students | Clients | Contacts | Buyer Contacts |
| First pipeline stage | New | Inquiry | Inquiry | Contact | Inquiry |
| Closing pipeline stage | Won | Enrolled | Closed | Repeat | Production |

Same buttons. Same screens. Same training. Different vocabulary that fits your team's daily reality.

---

## User flows

Below are the typical journeys for the three primary roles. Every flow shown here is identical in structure across all five industries — only the words change.

### Flow 1 — Salesperson's daily journey

```
1. Log in
   ↓
2. See "My Open Leads" stat: 12 active, 3 added today
   ↓
3. Open the highest-priority lead
   ↓
4. Read activity timeline — last 5 interactions
   ↓
5. Make a call, log the call as an Activity
   ↓
6. Move lead from "Contacted" to "Qualified" stage
   ↓
7. Schedule a follow-up Task for next Tuesday
   ↓
8. When ready, click "Convert to Deal" — system creates the Deal,
   links the Contact, marks the lead as Converted
   ↓
9. Open the Kanban board, see the new Deal in the first column
   ↓
10. Update Deal value, expected close date, notes as the conversation progresses
```

**Industry adaptation:**
- For an education counselor, "Convert to Deal" reads "Convert to Enrollment" and the next stage is "Profile Created."
- For a real-estate agent, the same button reads "Convert to Property Deal" and the next stage is "Site Visit."
- The salesperson never sees a generic term that doesn't apply to their world.

### Flow 2 — Branch manager's weekly review

```
1. Log in
   ↓
2. See branch-wide stats: total Leads, Conversion rate, Total Deal value
   ↓
3. Open Lead list, filtered to branch only
   ↓
4. Sort by stage — see who's stuck where
   ↓
5. Open a stuck lead, review timeline, message the assigned salesperson
   ↓
6. Open the Kanban board to see all branch Deals across all stages
   ↓
7. Identify Deals that haven't moved in 14 days
   ↓
8. Reassign one Deal to a different salesperson if needed
   ↓
9. Export the week's converted Deals to share in the Monday meeting
```

**Manager scope rule:** managers automatically see only their branch — they cannot see other branches' data even if they go looking. Admins see everything.

### Flow 3 — Admin's first-time setup

```
1. Sign up for Taskco
   ↓
2. Choose your industry profile (General, Education, Real Estate, Pharma, Garments)
   ↓
3. The system seeds your CRM with:
      - Industry-specific pipeline stages
      - Pre-built custom fields (IELTS Score, Property Type, etc.)
      - Auto-assignment rule for incoming leads
      - Branded labels ("Applications" instead of "Leads", etc.)
   ↓
4. Invite your team — assign roles (admin, manager, salesperson)
   ↓
5. Optionally tweak: add custom fields, add team branches
   ↓
6. Done — your team can log in and start working in minutes
```

**No development required.** Choosing an industry profile is a single dropdown click. The CRM reconfigures itself.

---

## Two real-world scenarios

These walkthroughs show the same software solving two completely different business problems, end to end.

### Scenario A — Study-abroad agency

> Rahim wants to study at a Canadian university. A counselor named Asha works the entire journey inside Taskco CRM.

| Day | What happens | Where in CRM |
|---|---|---|
| Day 0 | Rahim fills out a website form. Taskco creates a Lead. The system auto-assigns it to Asha. | Lead created → workflow auto-assigns owner |
| Day 1 | Asha calls Rahim, logs the call, schedules a counseling session. | Activity logged against Lead |
| Day 7 | Counseling done — Rahim is shortlisted for University of Toronto. Asha clicks "Convert to Enrollment." | Lead → Enrollment (Deal) |
| Day 10 | Rahim uploads passport, IELTS certificate, transcripts. | Document module attaches files to the Enrollment |
| Day 14 | Asha submits the application. Stage moves to "Applied." | Kanban board, drag stage |
| Day 30 | Offer letter received. Stage moves to "Offer Received" — Rahim gets an automated email. | Workflow rule: stage change → notify |
| Day 60 | Visa approved. Stage moves to "Visa Processing → Enrolled." Invoice generated automatically (v1.5). | Workflow action: deal won → create invoice |
| Day 65 | Rahim pays. Asha marks the Enrollment as Won. The agency books revenue. | Final stage — Won |

Total touchpoints: 8. Total CRMs: 1.

### Scenario B — Real-estate agency

> Maya is hunting for a flat in Dhaka. An agent named Karim handles her from inquiry to closing.

| Day | What happens | Where in CRM |
|---|---|---|
| Day 0 | Maya calls about a listing. Karim creates a Lead with budget and location. | Lead created with custom fields (Budget, Location) |
| Day 2 | Karim takes Maya on a site visit. Logs it. Stage moves to "Site Visit." | Activity + stage change |
| Day 5 | Maya wants to negotiate. Karim clicks "Convert to Property Deal." | Lead → Property Deal |
| Day 10 | Negotiation goes back and forth. Karim logs every offer. | Activity timeline |
| Day 15 | Deal agreed at 50 lakh. Stage moves to "Booking." | Workflow: stage change → notify branch manager |
| Day 16 | Maya pays 5 lakh booking fee. Invoice issued. | Invoice integration (v1.5) |
| Day 30 | Agreement signed. Stage moves to "Closed." | Final stage — Closed |

Same software as Scenario A. Different vocabulary, different stages, identical workflow capability.

---

## What you can customize without a developer

Once your industry profile is active, your team can still tailor the CRM further:

| Customization | How |
|---|---|
| Add a new field to a Lead | Pack JSON edit (admin) or upcoming admin UI |
| Add a new stage to your pipeline | Same |
| Rename a stage | Same |
| Add a new automation ("When deal stalls 7 days, notify manager") | Workflow rule entry |
| Reassign a lead to a different salesperson | Click on the lead |
| Promote a salesperson to manager | Role assignment in user settings |

What requires a developer: adding entirely new modules (e.g., a "Property Listings" module is a v2 add-on for real-estate tenants). Everything inside the existing modules is configurable.

---

## Multi-tenant isolation — what it means for you

Each company on the platform gets its own:

- **Database** — your customer list is never visible to other Taskco customers, even by accident.
- **Users** — your team's logins exist only in your tenant.
- **Customizations** — adding a custom field or rule for your company affects only your team.
- **Industry profile** — switching between profiles is a one-time provisioning choice.

You share infrastructure (servers, software updates) but no data. This is the same isolation model used by enterprise SaaS platforms like Shopify and Atlassian.

---

## What's shipping when

| Version | Modules | Status |
|---|---|---|
| **v1** | Lead, Deal, Contact, Activity, Support, Document | Building now — single shippable release |
| **v1.5** | Communication (Email + WhatsApp), Invoice integration | After v1 stable in production |
| **v2** | Domain apps (University catalog for Education, Property listings for Real Estate), AI features (auto-recommendations, success prediction) | After paying customers ask for vertical depth |

Detailed phasing: see [`roadmap.md`](roadmap.md).

---

## Frequently asked questions

**Q: Do I need to change anything about my business process to use this?**
A: No. The CRM is configured to match your industry's existing process. If your process changes, the CRM follows.

**Q: Can my education team and my real-estate team use the same Taskco account?**
A: Each tenant runs one industry profile. If you have two business arms, you run two tenants. They share infrastructure but have separate data.

**Q: What happens if my industry isn't on the list?**
A: The General profile is a generic CRM with no industry-specific assumptions. A new industry pack can be added by your developer in days, not months — only JSON configuration, no engine code.

**Q: How is data secured?**
A: Each tenant has an isolated database. Role-based access controls prevent salespeople from seeing each other's data within a tenant. All access is authenticated and logged.

**Q: Can I export my data if I leave?**
A: Yes. CSV export is available on every list page (v1). Full data export to JSON is v2 (Pack import/export panel).

**Q: Will my customizations break when Taskco releases an update?**
A: No. Pack updates are additive-only — your custom fields, stages, and rules are never overwritten or deleted by a system update.

---

## Where to go next

| If you want to... | Read |
|---|---|
| See the technical architecture | [`crm_plan.md`](crm_plan.md) |
| Understand the phased delivery | [`roadmap.md`](roadmap.md) |
| Author a new industry profile | [`guides/pack-authoring.md`](guides/pack-authoring.md) |
| See user-flow specs per industry | [`packs/`](packs/) folder |
| See engine specs | [`engines/`](engines/) folder |