Implementation Keycrm

Homepage - dashboard. Statistics - Tasks, payments, clients BASE 1: "Clients" (Table view) Properties: - Name (Title) - Company (Text) - Phone (Phone) - Address (Text) - Email (Email) - Notes (Text) - Files (attachment) - Regular client (checkbox) - Service (Multi-select: Bookkeeping, Payroll, Accounting, Business formation, Taxes, Support, Other) - Tasks (Relation → base "Tasks", bidirectional link, shows related tasks directly in the client card) with current status - Payments (Relation → base "Payments", bidirectional link) with current status - Meetings (Relation → base "Meetings", bidirectional link) BASE 2: "Payments" (Table view, separate base for payment history) Properties: - Amount (Number, format — currency) - Client (Relation → base "Clients") - Date (Date) - Status (Future, Invoice, paid). - Notes (Text) Add quick filters with statuses and date ranges. Button to download csv. Add to the client card Rollup "Total of all payments" (sum) and a table of related payments for viewing history. Dashboard for payments. Total money paid for the week, month. Total future payments BASE 3: "Tasks" (Board/Kanban view) Properties: - Task name (Title) - Client (Relation → base "Clients"). Allow new value for leads, or Text, if not yet a client - Task date (Date, ability to add exact time) - Date (Date, current default) - Timetracker (automation - integrate a button for tracking time spent on each task) - Description (Text) - Estimate (Number, optional, format — currency) - Task type (Select: Sale, Bookkeeping, Accounting, Payroll, Business Formation, Taxes, Other) Set up Board view with grouping by status (new, today, tomorrow, future, on hold, archive). Separately display a table of all archived tasks with a button to download a csv file sorted by parameters BASE 4: "Meetings" (Calendar view) Properties: - Date (Date) - Start time (include time in the same Date property) - Client (Relation → base "Clients", allow new value for leads, or Text, if not yet a client) - Notes (Text) Display as Calendar view by property "Date". BASE 5. Regular clients - Name (Relation - Base Clients Name) - Company (Relation - Base Clients Company) - Amount (Number, format — currency) - Period (Select: Month, quarter, year) - Service (Relation - Base Clients Service (Multi-select: Bookkeeping, Payroll, Accounting, Business formation, Taxes, Support, Other)) - Notes (Text) - Dept (Relation - Base Payments - status Invoice)

Set up marketing trigger emails. It's better to discuss the details and the cost of the services as well. Thank you.

There is a ready web tool for the sewing industry — the interface is made, part of the logic is there, but real integrations are not connected. It needs to be brought to a working state. Demo: https://prognoz.rich2222shop.site/Goal The system must accurately show how many and what positions (size/color) need to be cut, see the total remaining (stock + in cutting + returns), and reduce re-sewing by accounting for the statistics of refusals.Tasks Integration with LP CRM — connect via API (key/subdomain fields are already available), pull in stock, orders, returns. Bypass CORS through a proxy on Render.com. Cutting calculation logic — finalize the formula Plan − Stock CRM − In cutting + Returns to work with real data, calculate based on the size×color matrix. Accounting for refusals in the forecast — the % of refusals by size/color should reduce the cutting plan for that position, not just be displayed. Unified total stock — consolidate stock + in cutting + returns into one table. Workshops and cutting history — distribution by workshops, acceptance of returns, history of transfers. Bug fixes — some buttons are currently placeholders, they need to be brought to a working appearance.Stack HTML/JS single-page, localStorage, integration with LP CRM API, proxy on Render.com.Requirements Experience integrating CRM via REST API (plus — experience with retailCRM/LP CRM) Experience with proxy/CORS Understanding of warehouse/manufacturing logic Willingness to improve existing code without rewriting from scratchWork format Communication in writing (chat/messenger) → phased delivery (CRM → calculation logic → stock/workshops → polishing) → demo at each stage. It is important to understand the essence of the task, not just to formally execute the terms of reference — it is welcomed if you propose your own solutions or improvements where you see that it can be made more convenient or reliable.Budget / Timeline Budget: 6000 UAH (negotiable depending on the scope and phased delivery)

It is necessary to implement a custom integration of the WayForPay payment system on a website that operates on the Wix platform. Ensure the possibility of online payment for services directly on the site with automatic updating of order statuses in the Wix database and correct transmission of these statuses for further routing in CRM systems.

A specialist in Keepin CRM is needed for further development of the already configured system. It is necessary to conduct an audit, optimize funnels, automation, and business processes, improve integrations, and make the CRM more convenient and effective for daily work. Further collaboration on administration and system development is possible. In your response, please indicate your experience with Keepin CRM and examples of completed projects.