What documents will we exchange, and when?
The table below lists the document flow from pre-engagement to closeout.
Client-facing reference. Last updated: July 2026 ยท hello@bsmdigitalworkforce.com
Our team replies within one business day.
We build and run digital workforce systems: AI automations, custom software, and AI-driven marketing engines that do work a team would otherwise do manually. We operate in three service lines: AI Automation, SaaS Development, and AI Marketing Solutions.
Small and mid-sized operators who have more work than headcount: home care and healthcare agencies, professional services firms, e-commerce and content businesses, and founders building software products.
Both. We ship client work on retainer and project terms, and we build our own SaaS products. Client engagements benefit from the tooling and playbooks that come out of our own builds.
We run a lean senior team augmented by our own AI systems. You work directly with the person building your solution with no account-manager layer and no offshore handoff.
Any repeatable business process we can hand to software: lead intake and qualification, appointment scheduling, document and form processing, CRM data entry, email and SMS follow-up, quoting, reporting, internal knowledge assistants, and voice or chat agents that handle first-line conversations.
We map the process, identify the highest-cost manual steps, build the automation against your existing tools (CRM, phone system, email, spreadsheets, EHR), test it in parallel with your current process, then cut over and monitor.
Usually no. We connect what you already use. We only recommend replacing a tool when the integration cost exceeds the cost of switching.
Every automation ships with defined confidence thresholds and human-in-the-loop escalation. Anything the system is not sure about routes to a person rather than guessing. We agree escalation rules with you before launch.
Yes. We build inbound and outbound voice agents with live transcription, natural speech, call routing, and CRM write-back. These are scoped separately from text-based automations because of telephony and compliance requirements.
Full production web applications: authentication, billing, admin consoles, dashboards, APIs, background jobs, and AI features. Typical stack is Next.js, PostgreSQL or Supabase, and Stripe, deployed on managed infrastructure.
Yes, after a paid technical audit. The audit tells us and you whether the right move is to extend, refactor, or rebuild. You receive the audit document whether or not you continue.
Both. MVPs are scoped to a single core workflow and a paying-customer test. Full builds add billing, admin tooling, reporting, and operational hardening.
You do, on final payment. See Section 4.5.
Yes, under a monthly care plan covering hosting oversight, dependency and security updates, monitoring, bug fixes, and a fixed allocation of change requests.
Positioning and messaging, an AI-assisted content engine (blog, email, social, video scripts), SEO and local search, landing pages and conversion tracking, lifecycle email and SMS, and monthly performance reporting.
It is AI-produced and human-directed. Strategy, positioning, brand voice, and final approval are human. Drafting and repurposing at volume are automated. Nothing publishes without review (yours or ours) per the approval rules in Section 4.3.
Search engines penalize low-value content, not the tool that made it. We publish content that is original, factually reviewed, and tied to real search intent, and we monitor rankings monthly.
No credible team does. We commit to output volume, delivery timelines, and reporting transparency. We forecast results from benchmarks and revise the forecast as real data arrives.
Engagement starts through seven stages: discovery, proposal and scope, agreement and deposit, onboarding, build, UAT and launch, then handover or retainer.
Weekly cycles. Each cycle has a defined deliverable, a demo, and a written update. You get a live environment from the first milestone.
A written status update every week, a demo at every milestone, and a shared channel for day-to-day questions. Response target is same business day.
Through the change-request process in Section 4.2, in writing, inside the shared workspace.
A single decision-maker, timely system access, feedback within agreed windows, and source material such as brand assets, existing content, and process documentation.
Two weeks of included post-launch support for defects, then either full handover with training and documentation, or transition to a care plan or retainer.
| Stage | What happens | Typical duration |
|---|---|---|
| 1. Discovery call | 30-45 min. We map your problem, current tools, volumes, and constraints. | 1 day |
| 2. Proposal and scope | Written scope, deliverables, timeline, price, assumptions, and exclusions. | 2-3 days |
| 3. Agreement and deposit | Signed agreement plus NDA or DPA as applicable. Deposit invoiced. | 1-2 days |
| 4. Onboarding | Access provisioning, kickoff, shared workspace setup, and success metrics agreed. | 3-5 days |
| 5. Build | Delivered in milestones with a demo at each milestone. | 2-10 weeks |
| 6. UAT and launch | You test against acceptance criteria, we fix, then go live. | 1-2 weeks |
| 7. Handover or retainer | Documentation, training, and credentials transfer or care-plan transition. | 1 week |
Scope is defined in the written proposal. Anything not listed as in-scope is out of scope.
Every proposal lists explicit exclusions and assumptions. Those terms govern delivery and must be reviewed carefully.
Discovery findings that materially change scope trigger a re-scope before work continues.
All changes are submitted in writing in the shared workspace.
BSM responds with an impact assessment covering cost, timeline, and knock-on effects.
Work starts only after written approval.
Retainers include monthly change allocation. Overflow is quoted separately or rolled to the next cycle.
Feedback is consolidated into one response per deliverable from the designated decision-maker.
Three business days. Silence past the window is treated as approval to keep timelines moving.
Two rounds of revision within scope. Additional rounds are billable.
At onboarding you choose full pre-approval, spot-check, or auto-publish with post-review.
Projects use deposit-to-start and milestone billing. Work pauses on overdue invoices.
Retainers and care plans are billed monthly in advance, auto-renewing, with 30 days notice to cancel.
Hosting, APIs, model usage, ad spend, and licenses are passed through at cost and billed to your accounts wherever possible.
Deposits are non-refundable once discovery work has begun.
You own all custom code, content, designs, and configurations built for you, transferring on final payment.
BSM retains pre-existing frameworks, internal libraries, prompt architectures, and general methodology. You receive a perpetual non-exclusive license as embedded in deliverables.
Third-party components remain under their own licenses. BSM uses permissively licensed dependencies unless approved otherwise.
Only with written consent, and BSM will anonymize details on request.
Same business day, Monday to Friday, 9am to 6pm ET.
For systems BSM hosts or maintains: acknowledged within 2 hours and worked continuously until resolved.
Triaged within 2 business days.
Defined per care plan tier.
BSM will not build systems designed to deceive, spam, scrape without permission, or evade platform terms.
Not without qualified human reviewer oversight for medical, legal, or financial domains.
No. Required agreements must be in place before launch.
BSM does not guarantee specific revenue, ranking, or lead-volume outcomes.
Either party may terminate with 30 days written notice.
All completed work, documentation, and credentials for work paid in full.
Work in progress is invoiced to the point of termination.
The table below lists the document flow from pre-engagement to closeout.
| Phase | Document | Produced by | Purpose |
|---|---|---|---|
| Pre-engagement | Mutual NDA | BSM (or yours) | Protects both sides before details are shared |
| Discovery | Discovery brief or process map | BSM | Written record of current state and pain points |
| Proposal | Statement of Work (SOW) | BSM | Scope, deliverables, timeline, price, exclusions |
| Agreement | Master Services Agreement | BSM | Governing terms; SOWs attach to it |
| Agreement | Data Processing Agreement | BSM | Required where personal data is processed |
| Agreement | BAA | BSM | Required for protected health information |
| Onboarding | Access and credentials checklist | BSM | What we need, from whom, by when |
| Onboarding | Brand and positioning doc | Joint | Voice, audience, claims, and do-not-say list |
| Build | Weekly status report | BSM | Progress, blockers, and decisions needed |
| Build | Change request form | You | Formal scope-change trigger |
| Build | Technical specification | BSM | Architecture, data model, and integrations |
| UAT | Acceptance criteria and test log | Joint | Objective definition of done |
| Launch | Runbook and admin documentation | BSM | How to operate the system |
| Launch | Credential handover record | BSM | Signed transfer of accounts and keys |
| Ongoing | Monthly performance report | BSM | Metrics against agreed KPIs |
| Close | Final deliverables package | BSM | Code, assets, docs, and IP transfer confirmation |
In one shared client workspace (Google Drive or your system of record) with this structure:
01_Agreements / 02_Discovery / 03_Specs / 04_Deliverables / 05_Reports / 06_HandoverClientName_DocumentType_YYYY-MM-DD_vN (example: Acme_SOW_2026-07-22_v2). Versions increment on every material change.
Electronic signature for contractual documents and written approval in the shared workspace for all other artifacts. Verbal approvals are confirmed in writing before action.
Active engagement documents for the life of the engagement plus 24 months. Contracts and invoices follow statutory retention requirements. Everything else can be deleted on request (see Section 6).
Only what the work requires, usually system access (CRM, email, hosting, ad accounts), process documentation, brand assets, and where needed, customer record data involved in automation.
Least-privilege named accounts under delegated or role-scoped access, not shared logins. Shared credentials, where unavoidable, are kept in encrypted password managers and rotated at handover.
In your infrastructure where possible. Where BSM hosts, data is in named cloud regions (US by default) with encryption in transit and at rest. Processors and regions are listed in your DPA.
No. Enterprise or API tiers are configured with training disabled and zero retention where available. Your data is used only to serve your workload.
Primarily Anthropic and OpenAI APIs, plus specialist providers for speech, voice, and media. Subprocessors are listed in your DPA and updates are notified before additions.
Yes under signed BAA with HIPAA safeguards including encryption, access controls, audit logging, minimum-necessary data flows, and BAA-covered providers. If feasible, data is de-identified.
Under GDPR-compliant DPA. You are controller and BSM is processor, operating on documented instructions and supporting subject requests with SCCs for transfers as required.
Only personnel assigned to your engagement under written confidentiality obligations. Access is provisioned at onboarding and revoked at handover or offboarding.
Data flows through the system and is minimized in storage. Sensitive log fields are masked and retention limits are set in the technical specification.
Written notification to your named contact within 24 hours of confirmed incidents affecting your data, followed by root cause, scope, remediation, and prevention details.
Yes. Full export in standard formats on request at no charge. On termination, data is deleted within 30 days of confirmed handover, excluding required legal records and expiring encrypted backups.
Yes. BSM can review and sign your paper or complete your vendor security questionnaire during onboarding.
Yes, supported via self-hosted infrastructure and where feasible locally-run models. Trade-offs in cost and capability are scoped explicitly.
Fixed price for defined-scope projects, monthly retainers for ongoing automation and marketing, and hourly for advisory or open-ended discovery. Final pricing is in the proposal.
Initial discovery calls are free. Deep technical audits and process mapping engagements are paid and credited against the project if you proceed.
Automations start in low four figures. SaaS builds are five figures and up depending on scope. Marketing and care plans are monthly retainers with a minimum three-month initial term.
Projects have no minimum commitment. Retainers start at a three-month minimum so performance data is meaningful.
Email hello@bsmdigitalworkforce.com with what you want built, your current tools, rough monthly volume, and your timeline and budget range. You will receive a response within one business day and a discovery call within three.
Send your scope and we will reply within one business day.
This FAQ is informational and does not itself constitute a contract. Where it conflicts with a signed Master Services Agreement, SOW, DPA, or BAA, those documents govern.