Project 01
Lead intake and follow-up
A connected inquiry form, shared lead record, and follow-up workflow for an agreed lead source and receiving team.
See deliverables and acceptance checksProject-based by default
A defined project. A working handoff.
We agree what the system needs to do, what you will receive, and how we will check the result. You receive a written scope and price before the build begins.
Price and timing depend on the workflow, connected systems, document volume, and testing required. Third-party charges are shown separately.
Practical first projects
Choose the problem you want to solve.
Project 02
Business knowledge organization
An organized business repository with a file inventory, agreed folder structure, current-document rules, and a tested handoff.
See deliverables and acceptance checksProject 03
AI assistant setup and review
A scoped AI assistant configuration with approved sources, explicit tool permissions, human handoffs, evaluation cases, and operating documentation.
See deliverables and acceptance checksCommercial model
From the first conversation to handoff.
Start with one useful outcome. We investigate uncertain requirements before committing to implementation.
Fit review
A short conversation establishes the problem, people, systems, urgency, and whether VBoarder is the right kind of help. No implementation promise is made here.
Paid discovery when needed
For unclear or multi-system work, discovery produces the current-state map, target workflow, risks, options, acceptance criteria, and build recommendation.
Scoped implementation
The approved build defines deliverables, exclusions, customer responsibilities, third-party costs, test plan, documentation, training, and handoff.
What the quote separates
Build cost is not the same as run cost.
VBoarder professional services
Discovery, design, implementation, testing, documentation, training, and the agreed handoff artifacts.
Third-party software and infrastructure
Hosting, databases, phone, models, automation tools, storage, security, and other vendor costs shown separately.
Customer responsibilities
Access, subject-matter review, approvals, data authorization, testing participation, and named system ownership.
Optional follow-on work
New workflows, support, or improvement work can be scoped later. It is not required to keep the delivered system hostage.
Fit filter
When a project makes sense.
A clear no is more useful than an expensive maybe.
| Good fit | Probably not yet |
|---|---|
| A repeated workflow with a visible business consequence | A general desire to “add AI” without a defined task |
| An owner or operator willing to show the real work | No access to the people or records that define the process |
| A named person who will own the system after handoff | A system nobody inside the business is expected to own |
| Acceptance criteria that can be tested | A promise of transformation with no observable done condition |