BSM Digital Workforce Frequently Asked Questions

Client-facing reference. Last updated: July 2026 ยท hello@bsmdigitalworkforce.com

Need a direct answer now?

Our team replies within one business day.

1. About BSM

What does BSM Digital Workforce do?

+

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.

Who do you work with?

+

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.

Are you an agency or a product company?

+

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.

How big is the team?

+

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.

2. Services

2.1 AI Automation

What counts as AI automation?

+

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.

What does a typical automation project look like?

+

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.

Do you replace our existing software?

+

Usually no. We connect what you already use. We only recommend replacing a tool when the integration cost exceeds the cost of switching.

What if the AI gets something wrong?

+

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.

Do you build voice agents?

+

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.

2.2 SaaS Development

What do you build?

+

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.

Can you take over an existing codebase?

+

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.

Do you build MVPs or full products?

+

Both. MVPs are scoped to a single core workflow and a paying-customer test. Full builds add billing, admin tooling, reporting, and operational hardening.

Who owns the code?

+

You do, on final payment. See Section 4.5.

Do you provide ongoing maintenance?

+

Yes, under a monthly care plan covering hosting oversight, dependency and security updates, monitoring, bug fixes, and a fixed allocation of change requests.

2.3 AI Marketing Solutions

What is included?

+

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.

Is the content AI-generated?

+

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.

Will AI content hurt our SEO?

+

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.

Do you guarantee results?

+

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.

3. Process

How does an engagement start?

+

Engagement starts through seven stages: discovery, proposal and scope, agreement and deposit, onboarding, build, UAT and launch, then handover or retainer.

How do you run the build phase?

+

Weekly cycles. Each cycle has a defined deliverable, a demo, and a written update. You get a live environment from the first milestone.

How often will we hear from you?

+

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.

How do we request changes?

+

Through the change-request process in Section 4.2, in writing, inside the shared workspace.

What do you need from us?

+

A single decision-maker, timely system access, feedback within agreed windows, and source material such as brand assets, existing content, and process documentation.

What happens after launch?

+

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.

StageWhat happensTypical duration
1. Discovery call30-45 min. We map your problem, current tools, volumes, and constraints.1 day
2. Proposal and scopeWritten scope, deliverables, timeline, price, assumptions, and exclusions.2-3 days
3. Agreement and depositSigned agreement plus NDA or DPA as applicable. Deposit invoiced.1-2 days
4. OnboardingAccess provisioning, kickoff, shared workspace setup, and success metrics agreed.3-5 days
5. BuildDelivered in milestones with a demo at each milestone.2-10 weeks
6. UAT and launchYou test against acceptance criteria, we fix, then go live.1-2 weeks
7. Handover or retainerDocumentation, training, and credentials transfer or care-plan transition.1 week

4. Rules and Policies

4.1 Scope

How is scope defined?

+

Scope is defined in the written proposal. Anything not listed as in-scope is out of scope.

What about exclusions and assumptions?

+

Every proposal lists explicit exclusions and assumptions. Those terms govern delivery and must be reviewed carefully.

What if discovery changes the project?

+

Discovery findings that materially change scope trigger a re-scope before work continues.

4.2 Change requests

How are changes submitted?

+

All changes are submitted in writing in the shared workspace.

How are changes evaluated?

+

BSM responds with an impact assessment covering cost, timeline, and knock-on effects.

When does work begin on a change?

+

Work starts only after written approval.

How does this work on retainers?

+

Retainers include monthly change allocation. Overflow is quoted separately or rolled to the next cycle.

4.3 Approvals and feedback

Who should provide feedback?

+

Feedback is consolidated into one response per deliverable from the designated decision-maker.

What is the standard feedback window?

+

Three business days. Silence past the window is treated as approval to keep timelines moving.

How many revisions are included?

+

Two rounds of revision within scope. Additional rounds are billable.

How is marketing content approved?

+

At onboarding you choose full pre-approval, spot-check, or auto-publish with post-review.

4.4 Payments

How are projects billed?

+

Projects use deposit-to-start and milestone billing. Work pauses on overdue invoices.

How are retainers billed?

+

Retainers and care plans are billed monthly in advance, auto-renewing, with 30 days notice to cancel.

How are third-party costs handled?

+

Hosting, APIs, model usage, ad spend, and licenses are passed through at cost and billed to your accounts wherever possible.

Are deposits refundable?

+

Deposits are non-refundable once discovery work has begun.

4.5 Intellectual property

What do we own?

+

You own all custom code, content, designs, and configurations built for you, transferring on final payment.

What does BSM retain?

+

BSM retains pre-existing frameworks, internal libraries, prompt architectures, and general methodology. You receive a perpetual non-exclusive license as embedded in deliverables.

What about third-party components?

+

Third-party components remain under their own licenses. BSM uses permissively licensed dependencies unless approved otherwise.

Can our project be shown as a case study?

+

Only with written consent, and BSM will anonymize details on request.

4.6 Service levels

Support response target?

+

Same business day, Monday to Friday, 9am to 6pm ET.

Critical outage response?

+

For systems BSM hosts or maintains: acknowledged within 2 hours and worked continuously until resolved.

Non-critical bug handling?

+

Triaged within 2 business days.

After-hours coverage and uptime?

+

Defined per care plan tier.

4.7 What we will not do

What work is out of bounds?

+

BSM will not build systems designed to deceive, spam, scrape without permission, or evade platform terms.

Can AI output be presented as professional advice?

+

Not without qualified human reviewer oversight for medical, legal, or financial domains.

Can you automate regulated data without proper contracts?

+

No. Required agreements must be in place before launch.

Do you guarantee outcomes?

+

BSM does not guarantee specific revenue, ranking, or lead-volume outcomes.

4.8 Termination

How can either party terminate?

+

Either party may terminate with 30 days written notice.

What do we receive on termination?

+

All completed work, documentation, and credentials for work paid in full.

How is partial work billed?

+

Work in progress is invoiced to the point of termination.

5. Document Workflow

What documents will we exchange, and when?

The table below lists the document flow from pre-engagement to closeout.

PhaseDocumentProduced byPurpose
Pre-engagementMutual NDABSM (or yours)Protects both sides before details are shared
DiscoveryDiscovery brief or process mapBSMWritten record of current state and pain points
ProposalStatement of Work (SOW)BSMScope, deliverables, timeline, price, exclusions
AgreementMaster Services AgreementBSMGoverning terms; SOWs attach to it
AgreementData Processing AgreementBSMRequired where personal data is processed
AgreementBAABSMRequired for protected health information
OnboardingAccess and credentials checklistBSMWhat we need, from whom, by when
OnboardingBrand and positioning docJointVoice, audience, claims, and do-not-say list
BuildWeekly status reportBSMProgress, blockers, and decisions needed
BuildChange request formYouFormal scope-change trigger
BuildTechnical specificationBSMArchitecture, data model, and integrations
UATAcceptance criteria and test logJointObjective definition of done
LaunchRunbook and admin documentationBSMHow to operate the system
LaunchCredential handover recordBSMSigned transfer of accounts and keys
OngoingMonthly performance reportBSMMetrics against agreed KPIs
CloseFinal deliverables packageBSMCode, assets, docs, and IP transfer confirmation

Where do documents live?

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_Handover

What is the naming convention?

ClientName_DocumentType_YYYY-MM-DD_vN (example: Acme_SOW_2026-07-22_v2). Versions increment on every material change.

How are documents approved?

Electronic signature for contractual documents and written approval in the shared workspace for all other artifacts. Verbal approvals are confirmed in writing before action.

How long are documents retained?

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).

6. Data Sharing, Privacy and Security

What data will you need from us?

+

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.

How is access granted?

+

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.

Where is our data stored?

+

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.

Do you use our data to train AI models?

+

No. Enterprise or API tiers are configured with training disabled and zero retention where available. Your data is used only to serve your workload.

Which AI providers do you use?

+

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.

Do you handle protected health information?

+

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.

How do you handle EU or UK personal data?

+

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.

Who on your side can see our data?

+

Only personnel assigned to your engagement under written confidentiality obligations. Access is provisioned at onboarding and revoked at handover or offboarding.

What about our customers data inside an automation?

+

Data flows through the system and is minimized in storage. Sensitive log fields are masked and retention limits are set in the technical specification.

How do you handle security incidents?

+

Written notification to your named contact within 24 hours of confirmed incidents affecting your data, followed by root cause, scope, remediation, and prevention details.

Can we get our data back or deleted?

+

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.

Will you sign our NDA, DPA, or security questionnaire?

+

Yes. BSM can review and sign your paper or complete your vendor security questionnaire during onboarding.

Can everything stay inside our environment?

+

Yes, supported via self-hosted infrastructure and where feasible locally-run models. Trade-offs in cost and capability are scoped explicitly.

7. Commercial

How do you price?

+

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.

Do you charge for discovery?

+

Initial discovery calls are free. Deep technical audits and process mapping engagements are paid and credited against the project if you proceed.

What are typical engagement sizes?

+

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.

Is there a minimum commitment?

+

Projects have no minimum commitment. Retainers start at a three-month minimum so performance data is meaningful.

8. Getting Started

How do we get started?

+

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.

  1. What process or product you want built
  2. The tools you currently use
  3. Rough volume (leads, calls, records, users per month)
  4. Your timeline and budget range

Still have a question?

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.