For agencies, consultants and studios
Your client said yes. We build the part you can’t staff.
Integrations, automation and custom development, behind your brand or beside you on the call. Scoped and priced in writing before work starts.
- Agencies
- Fractional executives
- Consultants
- MSPs
- Studios
- Boutique dev firms
Yours to keep, with or without us
Build the scope sheet for your project
Tick what the project involves. The sheet lists what to collect from the client, what to settle before anyone prices it, what “done” means and what the handoff should hold. Copy it or download it.
A starting list, not a quote. It holds general delivery practice; nothing on it is specific to Illuminare, so it is as useful in your own proposal.
What a handoff looks like
Everything you need to run it without us
Open each part of the packet. Whoever takes the work over, you or your client, gets the same five things. The samples show the format, not a client file.
Repository, in your or your client’s organizationSample
project/ README.md how to run it src/ the code tests/ checks that were run deploy.md how it ships runbook.md day to day
Who owns whatSample
| Service | Owner | Access after handoff |
|---|---|---|
| Hosting | Client | Client admins |
| CRM | Client | Client admins, partner on request |
| Source code | Partner or client | Named people only |
| Domain and DNS | Client | Client admins |
runbook.mdSample
- What it does in two sentences
- Where it runs and who pays for it
- How to tell it is working, with the one place to look
- What to do when it fails, step by step
- How to turn it off and what happens next
Test recordSample format
| Check | Run against | Result |
|---|---|---|
| Form entry reaches the CRM | A test record | Pass or fail, dated |
| Failed sync raises an alert | A forced failure | Pass or fail, dated |
| Weekly report matches a hand count | A sample week | Pass or fail, dated |
One page per integrationSample
- What it does
- Sends each new form entry to the CRM.
- Turn it off
- Disable the sync step in the automation settings.
- What changes
- New entries stay in the form inbox until it is turned back on.
Two ways to work together
You decide who the client hears from
Pick one and see who talks to whom. Who speaks to the client, and when, is agreed in writing first.
- You own the client relationship and the conversations.
- We build, test and document. You present the work as yours.
- We stay out of your client’s inbox unless you bring us in.
- You introduce us for a defined part of the work.
- We join the calls and sessions that part needs, and no others.
- Who speaks to the client, and when, is agreed in writing first.
How a project runs
Five steps, all in writing
Brief
You send the project in a few lines. The reply comes by email with questions, a fit decision or a next step.
Scope and price
A written proposal or SOW says what gets built, how it is tested and what it costs, before any work starts.
Deposit
Work starts on a deposit or a prepaid milestone, as the proposal sets out.
Build and test
Updates come in writing at the points agreed. Each piece is tested before you see it.
Handoff
Code, accounts and a written runbook, so you or your client can run it without us.
What you can check before you send a client our way
Checkable, not promised
Work you can open
This site moved off WordPress with every URL kept and its forms, booking and popups rebuilt. Read the case study.
Yours to keep
Code, accounts and data stay in your name or your client’s. Each integration has a one-page description of what it does and how to turn it off.
Tested before you see it
Integrations are tested against real records and sites are walked end to end before handoff.
One accountable builder
Nick Bostic, with more than 15 years in go-to-market, revenue operations and marketing technology, writes the plan and builds it. About Illuminare.
Included
- The scope in the signed proposal
- Written updates at the agreed points
- Testing, documentation and the handoff
- A priced change order for anything new
Only when the contract says so
- Standing or open-ended meetings
- A seat in your team chat
- On-call or after-hours response
- An open-ended retainer
Partner and client work stays confidential. No partner or client is named on this site without written permission. Industry-agnostic, with deep experience in life sciences and health tech when your client works under compliance review.
Share a project brief
A few lines are enough. The reply comes by email, with questions, a fit decision or a proposed next step.
The brief is used only to reply about this project. It is stored in the site's database and sent to our inbox by email, as the Privacy Policy describes.