> ## Documentation Index > Fetch the complete documentation index at: https://docs.lynkacrm.com/llms.txt > Use this file to discover all available pages before exploring further. # What Lynka is and how the parts connect > Understand Lynka as a connected CRM and business management platform for entrepreneurs and small teams, including LeadGen, Sales, Agreements, Inventory, Accounting, Support, Marketing, Reports, and team controls. Lynka is built for businesses that are too busy to keep rebuilding the same information in different tools. A customer should not need one spreadsheet for prospects, another for stock, a CRM for follow-up, a separate quotation tool, a separate invoice tracker, and then a different system to explain the money. Lynka does not pretend every business process is identical, but it gives those processes a shared set of customers, products, responsibilities, and records. ## Think in connected business steps The easiest way to understand Lynka is to follow the work. **Find someone to sell to.** LeadGen can start a prospecting run using targeting inputs supported by the current workflow. The result is still a prospect. It has not been qualified simply because Lynka found it. **Decide whether the prospect is real.** Sales uses Leads for early qualification. Activities, ownership, notes, email context, and follow-up help your team decide whether the opportunity deserves more time. **Create the commercial opportunity.** Qualifying a lead creates the related Deal only after Lynka's readiness checks pass. The Deal is where value, probability, expected close date, pipeline stage, and final won or lost outcome belong. **Make the offer.** A Quote is a proposal. It can have products, pricing, tax, terms, revisions, validity, and document output without pretending money is already owed. **Ask for payment.** An Invoice is different from a Quote. It records the amount the customer owes. Payment records then change what remains outstanding. **Move stock when the business sells or buys products.** Inventory keeps Products, Suppliers, Purchase Orders, Goods Receipts, stock movements, receiving conditions, reorder levels, and product margin connected. **Turn operations into financial records.** Accounting provides the ledger, receivables and payables context, journals, cash, bank reconciliation, tax settings, close controls, and financial statements. **Keep the customer after the sale.** Support Tickets connect service work to customers and can use assignment, priority, SLA logic, automation, and reporting. ## Why Lynka keeps separate records A common question is why Lynka does not use one giant "customer" record for everything. Because different records answer different business questions. | Record | The question it answers | | -------------- | ----------------------------------------------------- | | Lead | Is this prospect worth pursuing? | | Deal | What opportunity are we trying to win? | | Company | Which customer organization does this work belong to? | | Activity | What happened, or what should happen next? | | Quote | What are we offering? | | Invoice | What does the customer owe? | | Payment | How much of the invoice has actually been settled? | | Purchase Order | What have we ordered from a supplier? | | Goods Receipt | What did we actually receive? | | Ticket | What customer issue are we responsible for resolving? | Keeping those meanings separate is what makes reporting useful later. If a Quote, Invoice, Payment, and Deal all meant "sale," you could not reliably answer whether a customer accepted an offer, whether an invoice is overdue, or whether the opportunity was actually won. ## Lynka is for small teams too Small team does not mean simple access. An owner may need workspace visibility. A salesperson may only need Sales and Agreements. A finance person may need Accounting and Agreements plus read access to Inventory. A support person may need Tickets without seeing the general ledger. One person can also belong to more than one team. Lynka models these separately: * **Workspace membership** decides whether the person belongs in the workspace. * **Product area access** decides which parts of Lynka the person can open. * **Action permissions** decide what the person can do there. * **Record scope** decides which records the person can see. * **Ownership** says who is responsible for a specific record. * **Team membership** groups people for collaboration and team-level visibility. That is why Teams is more than extra logins. ## What Lynka should replace, and what it should not Lynka can replace many disconnected operating lists and tools when the same customer, product, or transaction is being copied between them. It is especially useful when sales, invoicing, stock, follow-up, and reporting need the same source records. It should not be treated as a promise to replace every specialist system in every country. A business with complex manufacturing, payroll, country-specific statutory filings, or other specialist requirements may still need dedicated systems. The docs explain what Lynka actually does and avoid claiming functionality simply because a neighboring category exists. ## The fastest way to learn Lynka Do not read every page from top to bottom. Pick one real job: Start with LeadGen, then follow the record through Sales and Agreements. See what changes from purchase order to receipt and stock. Give people the access they need without giving everybody owner access. Connect invoices and payments to the Accounting view of the same business activity.