Version: v1
Owner: Head of Development (HOD)
Status: Active
Last Updated: June 2026
Part of: AIS Master Service Documentation
Audience: The placed AI Specialist (you) — internal document
You've been placed — embedded inside a client's business as their dedicated AI Specialist, with the whole REMAP team behind you. You're never out there alone.
This document is for you: what to do in your first 30 days, when, and where to get help. Read it before your kickoff call.
The one thing that matters most in week one: put something tangible in front of the client's decision-maker, fast. Not a status update or a plan — something they can see: a working website, branding, an automation built in Claude Code, a design or UI on Vercel. Clients form their impression of you in the first few days. Land a real artifact early and the rest runs on goodwill.
REMAP preps the engagement before you start. It reaches you one of two ways:
Either way you'll have an agreed plan: a prework document the client follows, plus a 30/60-day project plan identified by our CEO. That plan is your main course of action for the whole engagement — everything you do ladders back to it.
Before day one: read the client briefing, read the plan and pick your first tangible target, confirm your setup (internet, camera, mic, dev environment), and confirm your hours — Full-Time (40 hrs/wk) or Fractional (20 hrs/wk), in the client's time zone.
You're an independent contractor delivering through REMAP. The client directs what to work on; REMAP supports how.
You're here to: implement AI through the agreed plan, enable and upskill the team to use AI themselves, train their staff for their specific field, share useful AI developments and resources, and advise on select projects. Taking on extra ad-hoc work and automations is expected — that flexibility is why they wanted a specialist. It's not scope creep to resist.
Hard lines — do not cross:
The guardrail: asked to do something at the edge of your role — strategy, another team, anything off-plan? Don't decide solo. Reach back to REMAP and we'll tell you what's in your remit.
Days 1–3: Kickoff. A call between you, the client, and REMAP within the first 3 working days. Lock down: working hours, communication tools, reporting cadence, your first-week tangible target, access and tooling, and who your primary contact is. If access isn't ready, chase it politely the same day — don't sit idle; escalate to REMAP if it's not cleared within 24 hours.
The tangible outcome — the centrepiece. By end of week one you deliver something real and decision-maker-facing. Target Wednesday (day 3); Friday is the hard deadline; sooner is better — if it's ready early, get it in front of them. Examples by engagement type:
Then communicate it clearly — show what it is and why it matters, in their terms.
Team training — a strong bonus. If time allows alongside the artifact, ask what AI platform they use (ChatGPT, Gemini, or Claude) and run one or two short lectures on using it well for their industry, with real use cases. Both is ideal — but if you can only do one, the tangible outcome comes first.
Week 1 showed direction; week 2 turns it into working software. Start building against the plan and keep progress visible — screenshots of working components are fine proof at this stage. Document and test your work before anyone relies on it.
Work the plan as your primary course of action. Take on ad-hoc work where it helps, but flag it if extra requests start threatening committed work. Hold a consistent rhythm — predictable hours and updates are trust at this stage. Document everything so nothing lives only in your head.
Three separate streams:
Full cadence detail — including Andrew's weekly check-in — lives in the AIS Check-in & Reporting SOP. Your weekly update uses the AIS Weekly Report Template.
Two kinds, and the difference matters:
Getting yourself unstuck on your own work is on us. Extra out-of-scope work the client wants is billable — flag it before it runs.
A tangible artifact in front of the decision-maker in week 1 (ideally Wednesday). Implementation underway by week 2. Steady delivery against the plan through weeks 3–4. Blockers raised early. You needing less oversight each week. The client thinking: "This was a good decision."
Public holidays are covered in a separate SOP.
| Window | Focus | Proof it went well |
|---|---|---|
| Days 1–3 | Kickoff; lock hours, tools, access, first-week target | Kickoff items all confirmed |
| Week 1 | Tangible, decision-maker-facing artifact (Wed target, Fri deadline) | Something real they can see |
| Week 2 | Begin implementation | Visible progress — screenshots fine |
| Weeks 3–4 | Steady delivery against the plan | Momentum building; less oversight |
| Day 7 | Check-in with REMAP | Friction surfaced early |
| Day 30 | Check-in with REMAP; client review | "Good decision" verdict |
REMAP AI · Private AI LLC · Internal Use Only · Confidential · v1