Lark Suite Internal System Setup

We are a six-to-ten-person sourcing and trading company working daily between Venezuela and Guangzhou, and we are rolling out Lark Suite (Feishu) as our single hub for teamwork. The platform will be brand-new to us, so the job covers everything from the initial workspace architecture to end-user hand-off.

Core scope

Lead pipeline (Lark Base) – capture new leads and track them through stages (Prospect → Quote → Production → Closed), with follow-up dates and reminders.
Client project tracker – a status board for active client projects through our sourcing lifecycle (sourcing, factory visits, production, logistics).
Messaging & collaboration – organize chats, groups, and video calls as our internal team workspace, replacing WeChat for day-to-day internal communication, with every employee moving seamlessly between desktop and mobile.
Task management – clear task lists and assignment flows linked to specific leads or projects.
File storage & sharing – a logical Drive hierarchy with permission rules that protect sensitive quotations while keeping day-to-day documents easy to reach.

Primary users
All employees will live inside this workspace; the configuration must be simple enough for factory-floor staff yet robust enough for managers tracking multiple client projects.

Deliverables

Workspace blueprint and agreed information architecture.
Fully configured Lark Suite instance with messaging, Drive, Docs, lead pipeline, and project/task modules active.
Short video guides or a live walkthrough session covering key features for the whole team.
Post-deployment checklist confirming security settings, backup options, and admin hand-over.

Acceptance criteria

Every employee can log in, find their teams, and send a message on day one.
A new lead can be entered and moved through the full pipeline without external spreadsheets.
New tasks can be created, assigned, and tracked end-to-end.
Shared Drive folders respect the permission matrix agreed in the blueprint.

We are bilingual (Spanish/English) and operate across China Standard Time and Venezuela Time; please be comfortable scheduling sync calls within those windows and documenting steps clearly so that no detail is lost in translation.

Timeline: looking to start within 1-2 weeks.