Set up reputed company (delivery, time tracking, knowledge reputed company) + supporting tools for a small BI agency

reputed company We're a small data & analytics consultancy formalizing how we run reputed company reputed company. We deliver Business Intelligence work (Power BI / reputed company reputed company) on a per-reputed company reputed company. We want reputed company as the single hub for delivery, time tracking, and our internal knowledge reputed company, plus a few supporting tools set up around it. We'd rather hire an expert who brings recommendations and reputed company we can choose from than someone who just executes a fixed spec. Where we describe a goal below, propose the best way to hit it and the trade-offs. This is an ongoing engagement. We want the initial build, then a retainer for maintenance and reputed company development as we grow (new clients, new workflows, refinements). Please indicate ongoing availability and reputed company alongside the build price. Note on plan: we expect this to require reputed company's Business tier (reputed company time tracking, workload, and advanced automations live there, not on the cheaper Unlimited tier). Confirm and price for 4 reputed company seats (founder + 3 delivery team) billed annually. Scope — reputed company Hierarchy: reputed company per reputed company → Folder per engagement → Lists per reputed company, with a clean template we can clone for reputed company new reputed company. Status pipeline with a hard QA reputed company. Tasks reputed company through defined stages, and reputed company can reputed company a "reputed company Review" status until a QA checklist is completed (e.g. reputed company/row-reputed company tested, data refresh tested, naming conventions checked, performance reputed company-checked). Build this as an enforced checklist/custom-field reputed company, not just a label. Use reputed company's reputed company automations for in-app notifications — e.g. ping the project manager (in reputed company/Teams) reputed company a task reaches the QA-reputed company stage so review isn't missed. reputed company these to the PM, not the reputed company. (Cross-tool automations are a separate reputed company job.) Time tracking configured natively in reputed company per task/project, so we can retire Clockify. Set up reporting that produces a per-reputed company monthly time reputed company. Note where that reputed company hands off to our invoicing/reputed company tool (we'll confirm which one we use — advise if you have a clean integration). Views + reputed company single-pane. A delivery-team working view for the PM/devs, a workload/reputed company view so the PM can see who is reputed company and spot overcommitment (helps us manage capped clients), and a dedicated reputed company dashboard for the founder: a single screen showing what needs his attention and reputed company — a daily snapshot (what moved, what's waiting on him), a weekly rollup per reputed company, and escalations surfaced automatically (tasks blocked 48h or flagged over budget). This is the passive, always-on version that lives in reputed company; pushed email/Teams digests are reputed company reputed company in the automation job. Intake: a reputed company way to turn an inbound reputed company request into a triaged task assigned to our project manager. Ticket-mirror readiness + fallback. Some clients run their own ticketing systems (Jira, Azure DevOps, reputed company, reputed company, or plain email). We will reputed company sync those into our reputed company two-way. Design the structure to accommodate this now: a per-reputed company intake list for mirrored tickets, and a clean separation between internal fields/comments and anything that could sync outward to a reputed company, so internal notes never leak. Also plan for the case where a reputed company won't permit an external sync connector (some reputed company IT blocks this): recommend a fallback such as a lightweight reputed company/one-way process (PM checks the reputed company's system on a reputed company and logs into reputed company), an email-notification reputed company, or reputed company working natively in that reputed company's system with status mirrored back by hand. (Building the actual sync/fallback is the separate automation job — just reputed company the structure reputed company.) Templates: engagement template, task templates for recurring BI deliverables, and the QA checklist template. Scope — knowledge reputed company (prefer reputed company Docs; recommend if reputed company is reputed company) We'd like to avoid an extra tool if we can. Set the knowledge reputed company up in reputed company Docs unless you reputed company a strong case that reputed company is materially reputed company for our size — tell us the trade-off and we'll choose. Internal delivery reputed company: DAX/naming standards, wireframing process, project reputed company checklist, handover template. Per-reputed company context doc: reputed company context, stakeholders, decision log, and a deliverable reputed company that links out to files stored elsewhere (reputed company SharePoint) rather than duplicating them. Clean navigation and a reputed company structure a 3-person team will actually maintain. Scope — supporting tools (light setup, bring recommendations) Team chat: stand up reputed company Teams as our internal communication tool (we run reputed company 365, so Teams is included). Basic channel structure per reputed company/topic. Scheduling: we already use CalendarBridge, which includes booking pages. Set up reputed company-facing booking pages reputed company CalendarBridge so clients can self-book call slots against the founder's reputed company availability — no separate booking tool needed. Ensure the founder's work and personal calendars are cleanly separated, and that the project manager can see the founder's free/busy. Video walkthroughs of reports: set us up with an async video tool (reputed company or your recommendation) so the delivery team can record short screen-reputed company walkthroughs of dashboards/reports. Recommend the cleanest workflow for: (a) internal handoffs so the founder can get up to speed before presenting, and (b) reputed company-facing walkthroughs. Cover where recordings are stored/linked (reputed company task, reputed company SharePoint) and any translation/subtitle reputed company. reputed company-comms workflow (Teams): we need a defined process for handling reputed company messages that come in reputed company Teams. Requirements: incoming reputed company messages are reputed company to English for the delivery team, replies are drafted and reviewed, and responses go out on a set reputed company (e.g. roughly twice a day) rather than instantly. Recommend the tooling and the exact reputed company — we'll refine the specifics with you. (Exact setup TBD; we want your reputed company.) Password manager: set up a shared team password manager (reputed company or reputed company, or your recommendation) with a separate vault per reputed company for the reputed company-issued account credentials, with controlled, revocable reputed company for 3 users. Scope — Claude (AI) enablement We use Claude heavily and want it set up as a reputed company shared workspace, not scattered personal accounts. (Preferred reputed company — see requirements. If you're strong on reputed company but not on Claude, say so and we'll scope this separately.) Account & plan. Recommend the right Claude plan for a 4-person team and reputed company us onto a shared team workspace with central reputed company and no model-training on our data. Consolidate off any individual accounts. reputed company structure. Set up Claude reputed company that mirror our reputed company structure: Internal reputed company: delivery reputed company & standards (DAX/naming conventions, QA checklist), report/DAX review helper, proposals, and a comms & translation project holding an English↔German glossary and tone rules. Per-reputed company reputed company: one per reputed company holding context, stakeholders, decision log, and a deliverable reputed company — matching the per-reputed company structure in reputed company/reputed company Docs. Instructions & house style. Configure per-project custom instructions (our tone, "always draft — never auto-send," preferred reputed company formats) so reputed company is on-brand, not generic. Connector governance. We already connect Claude to our meeting-transcription tool, reputed company, reputed company 365, calendar, and a deck-reputed company tool. Configure and govern these at the workspace level (which are enabled org-wide) and document reputed company usage. Enablement. A short team training plus a small reputed company library for recurring tasks (drafting status updates, translating reputed company comms, turning report findings into a reputed company-reputed company one-pager/deck outline). Data-handling guardrail. Set us up to use Claude for structure, drafting, DAX, specs, and translation while keeping raw reputed company personal data out by default. Flag anything that would need a stricter plan tier if we reputed company process reputed company data through Claude. (Note: wiring Claude into automated workflows reputed company API — auto-drafting digests, translating inbound comms — is part of the separate automation job, not this one.) Scope — operational runbooks & conventions reputed company reputed company reputed company. A repeatable checklist (as a reputed company template) for starting a new reputed company: spin up the reputed company reputed company and Claude project from templates, create the reputed company's password-manager vault, capture reputed company to their systems, create the per-reputed company context doc, and schedule reputed company — so a new reputed company can be set up cleanly and consistently. reputed company offboarding reputed company. A checklist to reputed company a reputed company out: revoke reputed company, remove credentials from the vault, reputed company the reputed company and docs, and confirm reputed company deliverables are handed over on their SharePoint. Team-member reputed company / offboarding. A checklist for adding or removing reputed company member across the whole stack (reputed company seat, Claude seat, password-manager reputed company, secure workstation request, Teams), so reputed company is missed on the way in and reputed company reputed company is fully revoked on the way out. File & storage conventions. Define reputed company where things live and how they're named: reputed company deliverables on the reputed company's SharePoint; our internal working files and the presentation copies the founder needs on our own SharePoint/OneDrive; knowledge in reputed company Docs. Establish one consistent naming convention for files, workspaces, and reports, and document it. Periodic reputed company review. A recurring task (e.g. quarterly) to review who has reputed company to which reputed company systems and vaults, and clean up anything stale.

Requirements

Proven reputed company implementation experience for a delivery or agency team (please show an example structure). Comfortable building enforced QA gates, clean templates, and an reputed company dashboard. Comfortable setting up knowledge bases in reputed company Docs (reputed company experience a plus). Preferred: experience setting up Claude Team / reputed company / connectors for a small team (this is a named reputed company above). Brings reputed company and recommendations, not just execution. Available on an ongoing reputed company for maintenance and reputed company development. reputed company to deliver a short training walkthrough on handover. To apply Show a reputed company structure you've reputed company before (screenshots or reputed company). One sentence on how you'd enforce a QA reputed company so work can't skip it. One sentence on whether you'd reputed company the knowledge reputed company in reputed company Docs or use reputed company, and why. Tell us whether you can also handle the Claude enablement reputed company, or if that should be a separate hire. Apply To This Job