Working Terms
Collaboration & Co-Creation Terms.
Plain-language working terms so we start clear. These cover sessions, projects, learning groups, beta testing, and participation in The Co.
These are general working terms for how I collaborate. They are not legal advice and haven't been reviewed by an attorney. A signed proposal or statement of work for a specific engagement supplements — and takes precedence over — anything here.
Scope & written confirmation
Every engagement begins with a written scope — a proposal, statement of work, email confirmation, or booking receipt — that names the deliverables, timeline, and fees. Work I take on is bounded by that written scope. New requests outside it become their own written scope before I begin.
Roles, responsibilities & communication
I show up prepared, on time, and honest about what I see. I ask the same in return. We communicate clearly and respectfully, name changes early, and reply within a reasonable window (usually 2–3 business days). Silence stalls the work — please tell me if something has shifted.
Fees, deposits, invoicing & expenses
Fees are named in the written scope. Most engagements require a deposit to hold the calendar. Third-party expenses (production, printing, venues, travel, collaborator fees, software, platform subscriptions) are quoted or reimbursed separately. Invoices are due on receipt unless stated otherwise; balances more than 14 days late may pause the work.
Scheduling, rescheduling & missed sessions
Sessions can be rescheduled with at least 24 hours' notice. No-shows and last-minute cancellations may forfeit the session. For multi-week engagements, unused hours in a given week don't automatically roll — we agree in writing when they do.
Confidentiality & consent
What you share with me stays with me. I don't quote, screenshot, or repurpose private conversations, decks, or working files without your permission. Recordings, transcripts, and AI-generated notes only happen with explicit consent — yours, and everyone else in the room.
Pre-existing intellectual property
You keep everything you brought in — your brand, your writing, your data, your code, your relationships. I keep the frameworks, methods, templates, prompts, and know-how I bring to the work. Ownership of new work created together is defined in the written scope for that engagement.
Attribution, portfolio & testimonials
I love naming collaborators. I may reference our work publicly (portfolio, case studies, social) unless you ask me not to — just tell me. Testimonials you offer are used with your permission and can be revised or withdrawn at any time.
Beta testing & product feedback
For beta testing, app and platform feedback, and product advisory: you provide access credentials and test data at your discretion, and you're responsible for what's in them. Feedback I give is honest, directional, and not a guarantee of product outcomes, market fit, or performance. I don't publish product details that aren't already public.
AI training & workflow sessions
In AI trainings and workflow builds, you're responsible for your tool accounts, keys, privacy settings, and permissions. Please don't paste sensitive personal, health, financial, or client data into shared prompts or third-party tools unless you've confirmed it's approved. I'll flag risks I see; the operating decisions stay with you.
The Co. & community expectations
In The Co., learning groups, working groups, and collaborative labs: keep what's shared in the room confidential unless the group agrees otherwise. Feedback is given respectfully and specifically. No harassment, no unsolicited extraction or selling to other members, no unauthorized recording. Credit collaborators when their contribution is real.
Non-exclusivity & independent contractor
Our engagement is non-exclusive — I work with other clients and collaborators, and so can you. I am an independent contractor, not an employee, partner, agent, or joint venturer of yours. Participating in a session, cohort, or The Co. does not create co-ownership of my business or your business.
Ending a collaboration
Either of us can end an engagement with written notice. Completed work is paid for; deposits cover work already committed to the calendar. I return files and materials that belong to you, and I keep working files and internal artifacts. We part cleanly.
Signed agreements take precedence
If a signed proposal, statement of work, or specific written agreement conflicts with these general terms, the signed document controls for that engagement.
Questions or something to add before we begin? Send me a note — I'm happy to talk it through.