--- # === IDENTITY === id: business/startup-hiring/remote-team-setup-guide/2026 canonical_question: "How do I set up a remote team — tools, async practices, time zone management, culture building for distributed teams?" aliases: - "Remote team setup guide for startups 2026" - "Async-first remote work practices" - "Distributed team tools and culture building" entity_type: execution_recipe domain: business > startup-hiring > remote team setup guide region: global jurisdiction: global temporal_scope: 2025-2026 # === VERIFICATION === last_verified: 2026-03-12 confidence: 0.87 version: 1.0 first_published: 2026-03-12 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: "AI-powered collaboration tools (Notion AI, Loom AI summaries, Slack AI) changed async workflows in 2025; zero-trust security became default for distributed teams; 4-day workweek adoption accelerated in remote-first companies" next_review: 2026-09-08 change_sensitivity: high # === CONSTRAINTS === constraints: - "Async-first does not mean async-only — maintain 2-4 hours of daily overlap for real-time collaboration across time zones" - "Documentation must be the single source of truth — any decision made in a meeting that is not written down does not exist" - "Zero-trust security (SSO + MFA) is non-negotiable for distributed teams — never use shared passwords or VPN-only access" - "Tool budget scales with team size — expect $50-150/person/month for core stack (communication + docs + project management + security)" - "Remote onboarding takes 2-3x longer than in-person — budget 2-4 weeks of structured ramp-up for each new hire" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs a remote hiring strategy, not team setup" use_instead: "Search knowledgelib.io for remote hiring strategy — no dedicated unit yet" - condition: "User is setting up a hybrid office+remote model" use_instead: "business/operations/office-strategy-decision/2026" - condition: "User has 50+ employees and needs enterprise-scale remote infrastructure" use_instead: "Search knowledgelib.io for distributed org design — no dedicated unit yet" # === AGENT HINTS === inputs_needed: - key: team_size question: "How many people will be on the remote team?" type: choice options: ["2-5 (co-founders/early team)", "6-15 (seed stage)", "16-50 (Series A)", "50+ (scaling)"] - key: technical_skill question: "What is the team's technical skill level?" type: choice options: ["non-technical (no-code only)", "semi-technical (can edit configs)", "developer (can self-host tools)"] - key: budget_for_tools question: "What's the monthly tool budget per person?" type: choice options: ["free tier only", "up to $50/person/month", "up to $150/person/month", "no limit"] - key: time_zone_spread question: "What is the team's time zone spread?" type: choice options: ["Same time zone", "2-4 hours apart", "6-8 hours apart (US-Europe)", "12+ hours apart (US-Asia/global)"] # === EXECUTION METADATA === execution: required_inputs: - name: "Team roster with locations and time zones" source: "founder or HR" format: "spreadsheet or list with name, role, city, UTC offset" - name: "Company values and working principles" source: "founder" format: "document listing 3-5 core values and work norms" - name: "Budget approval for tool stack" source: "founder or finance" format: "approved monthly budget per person for SaaS tools" outputs: - name: "Remote operations handbook" format: "document" description: "Company-specific handbook covering communication norms, tool usage, meeting cadence, and escalation paths" - name: "Configured tool stack" format: "configured platform" description: "All communication, project management, documentation, and security tools provisioned and configured" - name: "Remote onboarding checklist" format: "document" description: "Week-by-week onboarding plan for new remote hires with buddy assignments and milestone checkpoints" tools_required: - name: "Slack" purpose: "Real-time messaging, channels, huddles" tier: "free/paid" cost: "$0 free tier / $8.75/user/month Pro" alternatives: ["Microsoft Teams", "Discord", "Twist"] - name: "Notion" purpose: "Documentation, wiki, knowledge base, project tracking" tier: "free/paid" cost: "$0 free tier / $10/user/month Plus" alternatives: ["Confluence", "Coda", "Slite"] - name: "Loom" purpose: "Async video updates, walkthroughs, demos" tier: "free/paid" cost: "$0 free (25 videos) / $15/user/month Business" alternatives: ["Vimeo Record", "Screencastify", "mmhmm"] - name: "Linear or Asana" purpose: "Project and task management" tier: "free/paid" cost: "$0 free tier / $8-10/user/month" alternatives: ["Jira", "Shortcut", "ClickUp", "Monday"] - name: "1Password or Okta" purpose: "Password management, SSO, MFA" tier: "paid" cost: "$4-8/user/month (1Password Teams) / $2-6/user/month (Okta)" alternatives: ["JumpCloud", "LastPass", "Bitwarden"] - name: "Calendly or SavvyCal" purpose: "Time zone-aware scheduling" tier: "free/paid" cost: "$0 free tier / $12-16/user/month" alternatives: ["Cal.com", "Reclaim.ai"] credentials_needed: - service: "Slack" type: "workspace admin account" where_to_get: "https://slack.com/get-started" free_tier_limits: "90-day message history, 10 integrations, 1:1 huddles" - service: "Notion" type: "workspace admin account" where_to_get: "https://www.notion.so/signup" free_tier_limits: "Unlimited pages, 10 guests, 5 MB uploads" - service: "1Password" type: "team admin account" where_to_get: "https://1password.com/teams/" free_tier_limits: "14-day trial only" estimated_duration: "1-2 weeks for full setup and rollout" estimated_cost: "$0 (free tier for 2-5 people) to $150/person/month (full enterprise stack)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/startup-hiring/remote-team-setup-guide/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)" # === RELATED UNITS === related_kos: depends_on: - id: "business/startup/first-10-hires-playbook/2026" label: "First 10 hires sequencing playbook — prioritized role order by founder skills and business model, comp benchmarks, equity allocation" feeds_into: - id: "business/startup-operations/employee-onboarding-playbook-for-startups/2026" label: "Startup employee onboarding playbook covering remote work mode — pre-boarding hardware shipping, tool provisioning, buddy program" related_to: - id: "business/startup-operations/meeting-cadence-design/2026" label: "Designing a startup's recurring meeting and communication cadence by company size — right-sized calendar, async alternatives, meeting hygiene rules" alternative_to: - id: "business/operations/office-strategy-decision/2026" label: "Remote vs hybrid vs office decision framework — structured 3-day hybrid as the 2025-26 default, function-mix and stage-based decision tree, attendance policy design" # === SOURCES === sources: - id: src1 title: "GitLab's Guide to All-Remote" author: GitLab url: https://handbook.gitlab.com/handbook/company/culture/all-remote/guide/ type: official_docs published: 2025-12-01 reliability: authoritative - id: src2 title: "How to embrace asynchronous communication for remote work" author: GitLab url: https://handbook.gitlab.com/handbook/company/culture/all-remote/asynchronous/ type: official_docs published: 2025-12-01 reliability: authoritative - id: src3 title: "How Doist Makes Remote Work Happen" author: Doist url: https://doist.com/how-we-work/how-doist-works-remote type: official_docs published: 2025-08-01 reliability: authoritative - id: src4 title: "Everything We Know About Remote Work" author: Buffer url: https://buffer.com/resources/remote-work/ type: industry_report published: 2025-10-01 reliability: authoritative - id: src5 title: "How to Manage Time Zones in a Global Remote Team" author: Deel url: https://www.deel.com/blog/managing-time-zones-in-remote-team/ type: industry_report published: 2025-09-01 reliability: established - id: src6 title: "Remote Team Culture: How to Build & Lead in 2026" author: Sembly AI url: https://www.sembly.ai/blog/remote-team-culture-how-to-build-lead-sustain-it/ type: industry_report published: 2026-01-15 reliability: established --- # Remote Team Setup Guide ## Purpose This recipe produces a fully operational remote team infrastructure — configured communication tools, documented async-first norms, a time zone overlap policy, virtual culture rituals, security/access setup, and a remote onboarding flow — enabling a distributed team to collaborate effectively from day one. [src1] ## Prerequisites - [ ] **Team roster with locations** available from founder or HR — list of names, roles, cities, and UTC offsets - [ ] **Company values document** available from founder — 3-5 core values and working principles - [ ] **Budget approval** — approved monthly per-person budget for SaaS tools - [ ] **Domain for email** — company email domain configured (required for SSO and tool provisioning) - [ ] **Admin access** — founder or ops lead has admin credentials for creating workspace accounts ## Constraints - Async-first is the default communication mode. Real-time meetings are reserved for relationship-building, brainstorming, and conflict resolution — never for one-directional status updates. [src2] - Every tool decision not written in the handbook is invisible to the team. Documentation is the single source of truth. [src1] - Minimum 2-hour daily overlap window across all time zones. Teams spanning 12+ hours require a "follow-the-sun" handoff protocol. [src5] - Zero-trust security posture: SSO + MFA on all tools, no shared passwords, device management for company data access. [src1] - Remote onboarding requires a structured 2-4 week program with assigned buddy — do not assume new hires will "figure it out." [src6] ## Tool Selection Decision ``` Which path? ├── Team size 2-5 AND budget = free │ └── PATH A: Bootstrap Free — Slack Free + Notion Free + Loom Free + Google Workspace ├── Team size 2-15 AND budget up to $50/person │ └── PATH B: Startup Standard — Slack Pro + Notion Plus + Linear Free + 1Password Teams ├── Team size 6-50 AND budget up to $150/person │ └── PATH C: Growth Stack — Slack Business+ + Notion Business + Linear/Asana + Okta + Loom Business └── Team size 50+ AND budget no limit └── PATH D: Scale Stack — Slack Enterprise + Notion Enterprise + Jira/Linear + Okta + Vanta + Loom Enterprise ``` | Path | Tools | Cost/person/mo | Setup Time | Security Level | |------|-------|----------------|------------|---------------| | A: Bootstrap Free | Slack Free, Notion Free, Loom Free, Google Workspace | $0-6 | 1-2 days | Basic (MFA only) | | B: Startup Standard | Slack Pro, Notion Plus, Linear, 1Password | $30-45 | 3-5 days | Good (SSO + MFA) | | C: Growth Stack | Slack Business+, Notion Business, Asana/Linear, Okta, Loom | $80-130 | 1-2 weeks | Strong (SSO + SCIM + device trust) | | D: Scale Stack | Slack Enterprise, Notion Enterprise, Jira, Okta, Vanta, Loom Enterprise | $150-250 | 2-4 weeks | Enterprise (SOC 2 + zero-trust) | ## Execution Flow ### Step 1: Select and Configure Communication Tools **Duration**: 2-4 hours **Tool**: Slack (or alternative) Set up the primary real-time communication platform with a channel architecture that separates signal from noise. ``` Channel structure (create these channels): #general — Company-wide announcements (posting restricted to leadership) #random — Watercooler, off-topic, social #team-{name} — Per-team channels (e.g., #team-engineering, #team-product) #project-{name} — Per-project channels (time-bound, archived when done) #standup — Daily async standups (bot-assisted or manual) #decisions — All decisions logged with context and rationale #kudos — Public recognition and wins #help-{topic} — Support channels (e.g., #help-it, #help-hr, #help-tools) ``` Configure notification defaults: set "Do Not Disturb" from 6 PM to 9 AM local time, disable @channel for non-admins, require threads for all replies. [src2] **Verify**: All team members can access workspace, channels are created, notification defaults are set. **If failed**: Check email domain restrictions, re-send invitations, verify SSO configuration. ### Step 2: Establish Async-First Communication Norms **Duration**: 4-6 hours (writing + team review) **Tool**: Notion (or documentation platform) Create the communication handbook section that defines when to use which channel and expected response times. This is the most critical step — without explicit norms, teams default to synchronous interruptions. [src3] ``` Communication norms document structure: 1. RESPONSE TIME EXPECTATIONS - @mention in Slack: respond within 4 business hours (not minutes) - Notion comment: respond within 24 hours - Email: respond within 24-48 hours - Emergency (outage/security): call or use #incidents channel — 15 min SLA 2. MEETING RULES - Default to async: "Could this be a Loom video or Notion doc instead?" - All meetings require a written agenda (shared 24h before) - All meetings produce written notes with action items (posted within 2h) - No meeting Wednesdays (company-wide deep work day) - Maximum 4 hours of meetings per person per week 3. ASYNC UPDATE FORMAT (daily standup) Post by end of your workday in #standup: - Done: What I completed today - Doing: What I'm working on tomorrow - Blocked: What I need help with (tag specific person) 4. DECISION-MAKING PROTOCOL - Write a proposal in Notion with context, options, and recommendation - Tag stakeholders with a review deadline (48-72 hours) - Silence = consent after the deadline passes - Log the decision in #decisions with link to proposal ``` Doist reports that 95% of their communication is async, with a 24-hour expected response window, and they have achieved 90% employee retention over 5 years with this model. [src3] **Verify**: Communication handbook is published, all team members have read and acknowledged it. **If failed**: Schedule a synchronous walkthrough session to answer questions and get buy-in. ### Step 3: Design Time Zone Overlap Policy **Duration**: 2-3 hours **Tool**: Notion + World Time Buddy or Similar Map your team's time zones and define collaboration windows. ``` Time zone mapping exercise: 1. List all team members with their UTC offsets 2. Identify the maximum gap (e.g., UTC-8 to UTC+5 = 13 hours) 3. Find the natural overlap window where most people are in working hours 4. Define two tiers: - CORE HOURS: 2-4 hours when ALL team members are available (e.g., 9 AM-1 PM ET = 3 PM-7 PM CET = 10:30 PM-2:30 AM IST) - FLEX OVERLAP: additional hours when most people are available (e.g., 1 PM-5 PM ET = 7 PM-11 PM CET) 5. Rules for core hours: - All synchronous meetings happen during core hours only - Core hours are for collaboration, not heads-down work - Rotate meeting times quarterly so no region always gets the worst slot ``` For teams spanning 12+ hours (e.g., US West Coast to Southeast Asia), implement a follow-the-sun handoff protocol: each shift writes a handoff note at end-of-day summarizing work completed, decisions pending, and blockers — posted in the relevant project channel. [src5] **Verify**: Time zone map published, core hours defined, all team members confirm the schedule works. **If failed**: If no reasonable overlap exists, split into sub-teams by region with async-only cross-team communication and one weekly sync. ### Step 4: Build Virtual Culture Rituals **Duration**: 3-4 hours (design) + ongoing **Tool**: Slack + Loom + Notion Remote culture does not happen organically — it must be designed and maintained. Build these five rituals: [src4] [src6] ``` Culture ritual calendar: WEEKLY: 1. Virtual coffee roulette (Mon) — random 1:1 pairings via Donut bot in Slack Duration: 15-30 min, unstructured, no work topics required 2. Team wins roundup (Fri) — async post in #kudos Each person shares: one win, one learning, one appreciation for a teammate BIWEEKLY: 3. Show & Tell (every other Wed) — 30 min synchronous during core hours 2-3 team members demo something they built, learned, or are excited about Record on Loom for those who can't attend live MONTHLY: 4. Virtual team activity (first Fri) — 60 min synchronous Rotate format: trivia, show your workspace, cooking together, online game Budget: $20-50/person for food/supplies delivered to their home QUARTERLY: 5. All-hands + retrospective (synchronous, 90 min) Company updates, OKR review, open Q&A, anonymous feedback collection Follow up with written summary and action items within 24 hours ``` **Verify**: Rituals are scheduled in shared calendar, Donut bot or equivalent is configured, first month of activities is planned. **If failed**: Start with just two rituals (coffee roulette + weekly wins) and add more as the team grows. ### Step 5: Set Up Security and Access Management **Duration**: 4-8 hours **Tool**: 1Password or Okta + device management Distributed teams have a larger attack surface than co-located teams. Implement zero-trust principles from day one. [src1] ``` Security setup checklist: 1. IDENTITY & ACCESS - [ ] Set up SSO provider (1Password, Okta, or JumpCloud) - [ ] Enforce MFA on all accounts (hardware keys preferred, TOTP minimum) - [ ] Create role-based access groups (Engineering, Product, Marketing, Admin) - [ ] Principle of least privilege: default to read-only, grant write access per-project 2. DEVICE SECURITY - [ ] Require full-disk encryption on all devices (FileVault/BitLocker) - [ ] Install endpoint protection (company-managed or BYOD policy) - [ ] Enable remote wipe capability for company data - [ ] Mandate automatic OS updates 3. DATA HANDLING - [ ] Define data classification (public, internal, confidential, restricted) - [ ] No company data on personal cloud storage (Dropbox, personal Google Drive) - [ ] Encrypted communication for confidential topics (Signal or E2E-encrypted Slack) - [ ] VPN for accessing internal services (if applicable) 4. ACCESS LIFECYCLE - [ ] Automated provisioning: new hire gets all accounts within 24 hours - [ ] Automated deprovisioning: departing employee loses all access within 1 hour - [ ] Quarterly access review: audit who has access to what ``` **Verify**: All team members have SSO + MFA enabled, access groups are configured, security policy is documented. **If failed**: If budget doesn't allow SSO, enforce strong unique passwords via 1Password Teams ($4/user/month) as minimum baseline. ### Step 6: Create Remote Onboarding Flow **Duration**: 6-8 hours (one-time design) **Tool**: Notion + Loom + Slack Design a structured onboarding program that takes new hires from zero to productive in 2-4 weeks. Remote onboarding fails when companies treat it as "send a laptop and a Slack invite." [src6] ``` Remote onboarding timeline: PRE-DAY 1 (1 week before): - Ship laptop + peripherals (webcam, headset, monitor if budget allows) - Send welcome email with: start date, first-day schedule, buddy assignment - Pre-provision all tool accounts (SSO makes this instant) - Add to #general and team channel in Slack WEEK 1: ORIENTATION - Day 1: Welcome call with manager (30 min) + buddy intro (30 min) - Day 1: Self-paced handbook reading (communication norms, values, security) - Day 2: Tool setup workshop (Loom recording available for async) - Day 3: 1:1s with each team member (15 min each, spread across the week) - Day 4: Shadow a team standup or project meeting - Day 5: First small task assigned (designed to ship within 1 day) WEEK 2: IMMERSION - Complete first project or meaningful contribution - Attend all recurring team rituals - Buddy check-in: 15 min daily, shifting to every-other-day by end of week - Manager check-in: 30 min mid-week WEEK 3-4: AUTONOMY - Own a workstream or project independently - Contribute to a decision proposal in Notion - Buddy check-in: twice per week, then as-needed - Manager 1:1: weekly 30 min (continues permanently) - 30-day feedback survey sent on Day 28 SUCCESS CRITERIA (Day 30): - [ ] Has shipped at least one meaningful deliverable - [ ] Can navigate all tools independently - [ ] Has met every team member 1:1 - [ ] Knows who to ask for what (documented in team directory) - [ ] Reports feeling "connected" on 30-day survey (score >= 7/10) ``` **Verify**: Onboarding template is published in Notion, buddy program is documented, first onboarding is scheduled. **If failed**: Start with a simpler 1-week checklist and iterate based on feedback from the first 3 hires. ## Output Schema ```json { "output_type": "remote_operations_setup", "format": "document_bundle", "components": [ {"name": "remote_handbook", "type": "document", "description": "Communication norms, tool usage, meeting rules, decision-making protocol", "required": true}, {"name": "tool_stack_config", "type": "configured_platform", "description": "All tools provisioned with channels, permissions, and integrations", "required": true}, {"name": "time_zone_policy", "type": "document", "description": "Core hours, overlap windows, meeting rotation schedule", "required": true}, {"name": "culture_ritual_calendar", "type": "calendar", "description": "Recurring events for team bonding and culture building", "required": true}, {"name": "security_policy", "type": "document", "description": "Access management, device security, data handling rules", "required": true}, {"name": "onboarding_checklist", "type": "template", "description": "Week-by-week onboarding plan with milestones and buddy assignments", "required": true} ], "completeness_check": "all 6 components published and accessible to team" } ``` ## Quality Benchmarks | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Async communication ratio | > 60% async | > 80% async | > 90% async | | Meeting hours per person per week | < 8 hours | < 5 hours | < 3 hours | | New hire time-to-productivity (days) | < 30 days | < 21 days | < 14 days | | 30-day onboarding satisfaction (1-10) | >= 6 | >= 7 | >= 9 | | Tool adoption rate (active users/total) | > 80% | > 90% | > 95% | | Security compliance (MFA enabled) | 100% | 100% | 100% + hardware keys | **If below minimum**: Revisit Step 2 (communication norms) — most failures trace back to unclear async expectations. If onboarding satisfaction is low, conduct exit interviews from the onboarding process and redesign Week 1. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | Team defaults to Slack for all communication (async norms ignored) | Norms not enforced, no accountability | Appoint a "communication champion" who redirects real-time requests to async channels; track async ratio weekly | | Meeting creep (hours increase over time) | No meeting budget or audit process | Implement hard cap of 4 meetings/person/week; require "could this be async?" check before scheduling | | Time zone resentment (one region always gets bad meeting times) | Meeting times not rotated | Implement quarterly rotation; record all meetings on Loom for async catch-up | | New hires feel isolated after onboarding | Buddy program stopped after Week 1 | Extend buddy pairing to 90 days; schedule monthly "how are you really doing?" check-ins | | Security incident (credential leak or unauthorized access) | Shared passwords or no MFA enforcement | Immediate: rotate all credentials; long-term: audit SSO compliance, enforce hardware MFA keys | | Tool sprawl (team using 3 chat apps, 2 doc tools) | No tool policy, individual preferences | Consolidate to blessed stack; block unsanctioned tools via SSO policies; migrate data within 30 days | ## Cost Breakdown | Component | Free Tier (2-5 people) | Startup ($30-45/person) | Growth ($80-130/person) | |-----------|----------------------|------------------------|------------------------| | Communication (Slack) | $0 (90-day history) | $8.75/user/mo (Pro) | $12.50/user/mo (Business+) | | Documentation (Notion) | $0 (unlimited pages) | $10/user/mo (Plus) | $18/user/mo (Business) | | Project management | $0 (Linear Free) | $0-8/user/mo | $10/user/mo (Asana Business) | | Async video (Loom) | $0 (25 videos) | $0 (free tier) | $15/user/mo (Business) | | Security (1Password/Okta) | $0 (personal vaults) | $4/user/mo (1Password Teams) | $6/user/mo (Okta SSO) | | Scheduling (Calendly) | $0 (basic) | $0 (basic) | $16/user/mo (Teams) | | Virtual activities budget | $0 | $10-20/person/mo | $30-50/person/mo | | **Total per person/month** | **$0** | **$33-51** | **$108-168** | ## Anti-Patterns ### Wrong: Replicating the Office Online Filling the calendar with daily standups, weekly all-hands, biweekly 1:1s, and ad-hoc "quick syncs" creates a remote team that is always in meetings and never doing deep work. GitLab's handbook explicitly states that meetings are for catalyzing async work, not replacing it. [src2] ### Correct: Async-Default with Intentional Sync Default to written communication (Notion docs, Loom videos, Slack threads). Reserve synchronous time for relationship-building, creative brainstorming, and conflict resolution. Track meeting hours per person and enforce a weekly cap. ### Wrong: Hiring Across All Time Zones Without a Policy Hiring the "best person regardless of location" sounds progressive but creates unmanageable overlap problems. A team spanning UTC-8 to UTC+8 has zero natural overlap hours, forcing someone to work nights permanently. [src5] ### Correct: Hire Within Overlap Constraints Define acceptable time zone bands before opening a role. State the required overlap hours in the job posting. For global teams, organize into regional sub-teams with async-only cross-team protocols. ### Wrong: Treating Remote Onboarding as "Send Laptop + Slack Invite" New hires who receive no structured onboarding in a remote setting report feeling lost and disconnected within the first week, leading to early attrition. [src6] ### Correct: Design a Structured 4-Week Program Assign a buddy, create a day-by-day schedule for Week 1, build in social time with every team member, and set a clear 30-day milestone. Measure success with a satisfaction survey. ## When This Matters Use this recipe when a founder or team lead needs to build the operational infrastructure for a distributed team from scratch — selecting tools, writing communication norms, designing time zone policies, and creating onboarding processes. Requires a team roster with locations, company values, and an approved tool budget as inputs. ## Related Units - [First Ten Hires Plan](/business/startup-hiring/first-ten-hires-plan/2026) - [Remote Onboarding Checklist](/business/startup-operations/remote-onboarding-checklist/2026) - [Team Communication Cadence](/business/startup-operations/team-communication-cadence/2026) - [Employer Brand Building](/business/startup-hiring/employer-brand-building/2026) - [Hybrid Work Policy](/business/startup-operations/hybrid-work-policy/2026)