How engagements actually work.

Plain language. No procurement process. No surprise clauses. If something here is unclear, email me and I’ll rewrite it.

Last updated 2026-04-18

1. What I promise

To deliver the scope written into your audit report or engagement agreement, in the timeframe quoted, at the price quoted. If something changes, I write it down and we both agree before the change happens. No scope creep, no silent add-ons, no surprise invoices.

2. What you pay for

The three engagement types, listed in full:

• Audit. $1,500, delivered in one week. You get a written report covering proposed architecture, SaaS consolidation opportunities, and prioritized automation roadmap. If you proceed to Foundation within 90 days, the full $1,500 is credited.
• Foundation. $8,000, delivered in 7 to 14 days. You get the full system build as specified in your audit report or engagement agreement. Includes 30 days of post-launch support.
• Ongoing. $2,500 per month, 3-month minimum, cancel anytime after. Continuous development, monitoring, and support. Monthly performance review.

3. What you own

Everything I build for you. The code, the database schemas, the dashboards, the automations, the AI query layer, the documentation. All of it. I hand over repositories and credentials at launch. If we part ways, you keep running the system without me.

I retain the right to reuse generic, non-proprietary patterns across clients (architecture templates, reusable code scaffolds). I never reuse anything specific to your business, your data, your customers, or your competitive position.

4. What I need from you

• Timely access to the accounts and systems we agreed to touch.
• A single point of contact at your company who can make decisions within 24 hours during an active build.
• Honest answers during the audit. The system quality compounds on that input.
• Invoice paid on time. Net 15 unless otherwise agreed.

5. Timelines and delays

I quote aggressive timelines (typically 10 to 14 days for a Foundation build) because I can. They depend on you being available for the handful of decisions I need during the build. If access is delayed or decisions stall, the timeline shifts by the same amount. I don’t charge for that dead time, but the calendar slides.

6. Payment terms

• Audit: 50% to kick off, 50% on delivery. Paid via ACH, wire, or card.
• Foundation: 50% to kick off, 50% on launch. Paid via ACH, wire, or card.
• Ongoing: Monthly, billed on the first of the month, due net 15.

Late payment (more than 30 days past due) pauses the engagement. I don’t chase invoices. If there’s a problem, email me directly and we’ll resolve it.

7. Refunds and cancellation

• Audit. Once the work has started (past the kickoff call), the initial 50% is non-refundable. If I fail to deliver the report in the agreed timeframe without a good reason, you get that portion back.
• Foundation. Refundable in full up to the kickoff call. Once the build begins, refunds are pro-rated against work completed.
• Ongoing. Cancel anytime after the 3-month minimum. Prepaid months already charged are credited to remaining work, then refunded if unused.

8. Liability

I build systems that touch real money flows. I take that seriously. I test before I ship, I set up monitoring, and I’m available to fix issues during the 30-day post-launch window.

That said: my total liability in any engagement is capped at the fees you’ve paid me for that engagement. If a bug costs you $100,000, I can’t cover that. This is standard for solo consulting work at this price point, and it’s why I’m obsessive about testing before anything goes live on production data.

I carry professional liability insurance. Details on request.

9. Confidentiality

Everything you tell me is confidential. I sign NDAs on request. I don’t reference clients by name in public case studies without written approval. I may reference anonymized patterns (industry, scale, stack) in marketing copy with no identifying details.

10. Termination

Either of us can end an engagement with written notice. I don’t hold work or access hostage. On termination, I hand over everything complete to that point, document where things stand, and revoke my access. You keep the invoice up to that date, I keep nothing.

11. Governing law

These terms are governed by the laws of the State of Texas, United States. Disputes resolved in Travis County if possible, through mediation first, then small-claims or arbitration as appropriate to the value of the dispute.

12. Changes to these terms

I may update these terms for new engagements. The version in effect for your engagement is whichever was current at the date you signed your engagement agreement. Updated versions never apply retroactively.

Contact

Email dan@dandelion.build with any question about this. Humans answer humans here.