FS-DOC-01Operations
Launch Plan
Device & Hardware Management
[YourCompany.com] · IT Department · Prepared by FullSpec · [Today's Date]
This Launch Plan gives you a clear picture of what is being built, how the build unfolds, and what FullSpec needs from you to get it live. It is written for the business owner and IT manager, not for a technical audience. FullSpec handles every stage of the build, testing, and deployment end to end. Your role is to provide tool access at the start and to confirm the automation is working as expected at the end.
01What you're launching
You are automating the full device and hardware lifecycle for your IT team, covering every event from a new hire receiving a laptop through to a leaver returning one and that device being wiped and restocked. Today, an IT coordinator manually touches twelve separate steps across each event, working across a stale spreadsheet, Jira tickets, Jamf, Gmail, and Slack with no single system in control. Three purpose-built agents will take over the lookup, record-keeping, communications, and MDM sync work, leaving only the physical handover and condition check with a human. The result is a live, accurate asset register updated in seconds, consistent outbound messages sent automatically, and overdue returns flagged the moment they are due, without anyone chasing a spreadsheet.
Process
Device & Hardware Management
Trigger
A new hire is confirmed, a leaver is flagged in HR, or a device request ticket is submitted in Jira
Final output
An updated Airtable asset record, a closed or updated Jira ticket, a Gmail confirmation sent to the employee, and a Slack summary posted to the IT channel
Agents being built
3 agents: Asset Register Agent, Device Lifecycle Comms Agent, MDM Sync Agent
Tools involved
Airtable, Jira, Jamf, Gmail, Slack, Google Sheets
Volume
Approximately 40 device events per month (assignments, returns, audits, repairs)
Launch PlanPage 1 of 4
FS-DOC-01Operations
02How the build works
FullSpec builds this automation across four structured stages: Connect, Build, Test, and Launch. Each stage has a defined set of actions and a clear handoff point. The build runs to a five-week schedule based on the Standard option you have selected, which covers all three agents and the Jamf MDM integration. You will have a named contact at FullSpec throughout and will only be pulled in at the moments listed below.
Complexity level: Moderate. Estimated delivery: 5 weeks (25 business days) from the close of Connect. The delivery clock starts at the close of Connect, not payment. Connect must be completed, credentials confirmed, and the configuration decision signed off before the build timer begins.
1Connect
Business days 1 to 3
FullSpec
Sends you a credential request form, reviews the existing Airtable base and asset register, documents all device event types (hire, departure, request), and identifies any data gaps that would cause problems at launch. Maps the Jamf API scope required.
You
Complete the credential form, share access to Airtable and Jira, confirm which MDM platform is in use, and make the one configuration decision detailed in Section 03. Respond within one business day to keep the clock running.
2Build
Business days 4 to 18
FullSpec
Builds the Asset Register Agent (Jira and Airtable availability lookup and record-write flows), then the Device Lifecycle Comms Agent (Gmail and Slack templates wired to Airtable triggers), then completes the MDM Sync Agent (Jamf API calls for enrollment and wipe on return). Tests each agent with sample events before moving to the next.
You
Available to answer questions if an edge case surfaces. No active work is required during Build unless FullSpec flags a data or access issue that needs your input.
3Test
Business days 19 to 22
FullSpec
Runs end-to-end tests across all three event types (new hire assignment, offboarding return, procurement trigger) and the quarterly audit flow. Tests the MDM wipe and re-enrollment in a Jamf sandbox. Validates that Airtable, Jira, Gmail, and Slack all update correctly in sequence.
You
Review a short test summary prepared by FullSpec, confirm that the outputs match your expectations, and sign off on User Acceptance Testing (UAT). Walk through the exception path for physical handover with your IT coordinator. Typically one 30-minute call.
4Launch
Business days 23 to 25
FullSpec
Switches the automation to live, monitors the first real events as they process, and confirms all three agents are running correctly. Delivers the full document suite (Runbook, Developer Handover Pack, Integration Spec, Test Plan). Provides a two-week monitored run period.
You
Notify your IT coordinator that the automation is live and that only the physical handover step remains manual. Flag anything unexpected to FullSpec at support@gofullspec.com during the monitored run period.
Launch PlanPage 2 of 4
FS-DOC-01Operations
03What FullSpec needs from you
FullSpec needs only access to your existing tools. No technical knowledge is required from you or your team. You do not need to set up any integrations yourself. The table below lists exactly what is needed for each tool and when. Everything in this list should be ready before Connect closes so the build can start without delay.
Airtable
Admin access to the workspace containing the device asset register base. A read/write API token scoped to that base.
Before Connect closes
Jira
A Jira user account (service account preferred) with permission to create and update tickets in the IT service project. API token for that account.
Before Connect closes
Jamf
A Jamf API role with permissions to read device records, assign MDM profiles, and trigger remote wipe commands. Confirm whether your instance is cloud-hosted or self-hosted.
Before Connect closes
Gmail
A Google Workspace account (shared IT mailbox recommended) with OAuth consent granted for sending mail. No password required, OAuth only.
Before Connect closes
Slack
A Slack app installation in your workspace with permission to post to the IT channel. FullSpec will provide the app manifest; you approve the installation.
Before Connect closes
Google Sheets
Read access to the current HR or asset spreadsheet used as a fallback data source, if applicable.
Before Connect closes
Before Connect closes, you must confirm one configuration decision: how hire and departure events will reach the automation. If your HR platform supports webhooks, FullSpec will connect directly. If it does not, the fallback is a daily sync from a shared Google Sheet maintained by HR. You need to confirm which approach applies and, if using the Google Sheet fallback, ensure HR agrees to keep it updated. This decision cannot be changed after the Build stage begins without resetting the timeline.
04Your role once live
Role
Ongoing responsibilities
What you no longer touch
You (business owner / IT manager)
Physically receive and inspect returned devices. Confirm the device condition and mark it received in Airtable when prompted by the automation. Review any procurement alerts posted to Slack by the IT manager prompt. Respond to FullSpec if a monitoring alert is raised during the two-week post-launch window.
Checking a spreadsheet for device availability. Drafting assignment confirmation emails. Manually scheduling audit reminders. Chasing staff for quarterly audit responses. Updating the asset register after each event. Logging Jira tickets for device assignments.
FullSpec
Monitors automation health during the two-week post-launch window. Available at support@gofullspec.com for any issues. Provides the full Runbook and SOP so your IT coordinator can handle exception events independently. Delivers all six documents in the suite for ongoing reference.
Not applicable. FullSpec does not perform ongoing manual IT operations.
Launch PlanPage 3 of 4
FS-DOC-01Operations
05What success looks like
Timeframe
What to expect
Sign of success
Week 1
The first real device events (hire, return, or request) process through the automation. Airtable records update automatically, Gmail confirmations go out, and Slack posts appear in the IT channel without manual input. Your IT coordinator handles only the physical handover step.
Zero manual register updates required for processed events. No missed confirmation emails.
Month 1
Approximately 40 device events have processed. The Airtable register is consistently up to date. The IT coordinator has been freed from routine record-keeping and email drafting. Any overdue returns have been flagged automatically on their due date rather than discovered at an audit.
IT coordinator reports at least 5 to 6 hours recovered per week. No ghost assets created during the month.
Month 3
The quarterly audit runs for the first time as an automated flow. Audit emails go out via Gmail, responses are collated automatically, and the reconciled register is ready without manual cross-referencing. The team can see the asset register is reliable enough to base procurement decisions on it.
Quarterly audit completed in under 1 hour of human time, down from 3 to 5 days of chasing. Asset register accuracy above 99%.
Next step: FullSpec will send you the credential request form within one business day of this plan being confirmed. Complete the form and return it, make the HR webhook decision noted in Section 03, and the Connect stage will close so the build clock can start. If you have any questions before then, reach out directly at support@gofullspec.com.
Launch PlanPage 4 of 4