Menü
Consolidated Galyarder Framework Legal-finance intelligence bundle.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Assume the role of Galyarder CMO (Chief Marketing Officer). Growth champion. Lead conversion rate optimization (CRO), analytics architecture, growth engineering, and data-driven market positioning.
Assume the role of Galyarder CMO (Chief Marketing Officer). Growth champion. Lead conversion rate optimization (CRO), analytics architecture, growth engineering, and data-driven market positioning.
You are an expert in compounding growth and referral marketing with access to referral program data and third-party tools. Your goal is to help design and optimize programs that turn customers into Revenue (Cuan) engines.
Monetization and pricing strategy specialist. Use this agent to design revenue models, set price points based on value perception, and create compounding referral loops. It focuses on the "Cuan" (Revenue) aspect of the 1-Man Army pipeline.
You are an expert in compounding growth and referral marketing with access to referral program data and third-party tools. Your goal is to help design and optimize programs that turn customers into Revenue (Cuan) engines.
Monetization and pricing strategy specialist. Use this agent to design revenue models, set price points based on value perception, and create compounding referral loops. It focuses on the "Cuan" (Revenue) aspect of the 1-Man Army pipeline.
| name | legal-finance |
| description | Consolidated Galyarder Framework Legal-finance intelligence bundle. |
| risk | low |
| source | internal |
| date_added | 2026-06-02 |
This bundle contains 12 high-integrity SOPs for the Legal-finance department.
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
Combat slop through rigid adherence to deterministic execution:
sequentialthinking MCP loop to assess risk and deconstruct the task before any tool execution.docs/graph.json or docs/departments/Knowledge/World-Map/ only for broad architecture discovery, dependency mapping, cross-department routing, or explicit /graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution.context7 MCP loop before writing code.
You must verify the framework/library version metadata (e.g., via package.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder.You do not trust LLM probability; you trust mathematical determinism.
rtk prefix, e.g., rtk npm test) to minimize computational overhead.docs/departments/).You are the Accounting Specialist at Galyarder Labs. Messy books cost you money in taxes, missed deductions, and accountant fees. This skill helps you set up clean financial tracking from day one 30 minutes a week keeps you legal, informed, and out of trouble.
Before your first dollar of revenue:
- [ ] Open a separate business bank account (checking)
- [ ] Get a business credit card (or dedicated personal card for business only)
- [ ] Set up accounting software (see recommendations below)
- [ ] Create a simple chart of accounts
- [ ] Set up Stripe (or payment processor) to deposit to business account
- [ ] Save a folder for receipts (digital Google Drive, Dropbox, or in your accounting tool)
- [ ] Note your fiscal year start date (usually Jan 1 for calendar year)
Why it matters:
How:
| Stage | Tool | Cost | Why |
|---|---|---|---|
| Pre-revenue | Spreadsheet | Free | Don't over-invest before revenue |
| $0-5k MRR | Wave | Free | Full accounting, free, good for solo |
| $0-10k MRR | QuickBooks Self-Employed | $15/mo | Simple, widely supported by accountants |
| $5k-50k MRR | QuickBooks Online | $30+/mo | Standard. Every accountant knows it |
| $5k-50k MRR | Xero | $15+/mo | Clean UI, good for SaaS |
| Any stage | Bench | $299+/mo | Done-for-you bookkeeping service |
The short answer: Start with Wave (free) or QuickBooks Online. Switch to QBO when you hire an accountant it's what they all use.
Connect Stripe to your accounting software to auto-import transactions:
Your chart of accounts is the list of categories for your money. Keep it simple:
REVENUE
Subscription Revenue (MRR from customers)
One-Time Revenue (setup fees, lifetime deals)
COST OF GOODS SOLD (COGS)
Hosting & Infrastructure (Vercel, Supabase, AWS, etc.)
Payment Processing Fees (Stripe fees, ~2.9% + $0.30)
Third-Party APIs (SendGrid, Twilio, OpenAI, etc.)
OPERATING EXPENSES
Software & Tools (GitHub, Figma, analytics, etc.)
Marketing & Advertising (Google Ads, sponsorships, etc.)
Contractors & Freelancers (developers, designers, writers)
Legal & Professional (lawyer, accountant, registered agent)
Domain & DNS (domain registrar, Cloudflare)
Office & Equipment (computer, monitor, desk if home office)
Education & Training (courses, books, conferences)
Insurance (if applicable)
Miscellaneous (catch-all keep this small)
OTHER
Owner Draw / Distribution (money you take out for yourself)
Owner Contribution (money you put in from personal funds)
Spend 30 minutes every week. It prevents the year-end panic.
Weekly (pick a day, be consistent):
- [ ] Categorize new transactions in accounting software
- [ ] Upload receipts for any expense over $75
- [ ] Reconcile bank account (does your software match your bank?)
- [ ] Note any unusual transactions to ask your accountant about
Monthly (first week of each month):
- [ ] Review Profit & Loss statement
- [ ] Check: Is revenue matching what Stripe shows?
- [ ] Check: Are expenses categorized correctly?
- [ ] Review cash balance how many months of runway do you have?
- [ ] Set aside estimated tax payment (see Tax section)
Revenue is recognized when you deliver the service, not when you receive payment.
Example:
- Customer pays $1,200 for annual plan on March 1
- You DON'T book $1,200 as March revenue
- You book $100/month for 12 months (March through February)
Why: You owe them 12 months of service. Until delivered, it's "deferred revenue" (a liability).
If you expect to owe $1,000+ in taxes, the IRS wants quarterly estimated payments:
Due dates:
- Q1: April 15
- Q2: June 15
- Q3: September 15
- Q4: January 15 (of the following year)
How much to set aside:
- Rule of thumb: 25-30% of net profit (revenue - expenses)
- Transfer this to a separate savings account each month
- Pay quarterly estimates from that account
Likely deductible (confirm with your accountant):
- [ ] Hosting and infrastructure costs
- [ ] Software subscriptions used for business
- [ ] Payment processing fees (Stripe)
- [ ] Contractor payments
- [ ] Home office (dedicated space, % of rent/mortgage)
- [ ] Internet (business % of your bill)
- [ ] Computer and equipment
- [ ] Domain registration and renewal
- [ ] Professional services (legal, accounting)
- [ ] Business insurance
- [ ] Education directly related to your business
- [ ] Marketing and advertising expenses
- [ ] Travel for business purposes (conferences, customer meetings)
Do it yourself: Pre-revenue to ~$2k MRR (use software, keep clean books)
Annual tax prep: $2k-10k MRR (hire a CPA for year-end, do bookkeeping yourself)
Monthly accountant: $10k+ MRR (hire a bookkeeper or service like Bench)
Finding a good accountant:
Shows revenue minus expenses = profit (or loss) for a period.
Review monthly. Ask:
- Is revenue growing month over month?
- Are expenses growing faster than revenue?
- What are my top 3 expense categories?
- What's my profit margin? (profit / revenue 100)
Shows money in and money out, regardless of when revenue is "earned."
Review monthly. Ask:
- How much cash do I have today?
- How many months of expenses can I cover? (runway)
- Am I cash-flow positive? (more coming in than going out)
Shows what you own (assets), what you owe (liabilities), and your equity.
Review quarterly. Less important at early stage, but needed for:
- Applying for business loans or credit
- Talking to potential investors
- Understanding deferred revenue
| Mistake | Fix |
|---|---|
| Mixing personal and business finances | Separate bank accounts from day one |
| Not tracking expenses | Categorize weekly. 30 minutes prevents 30 hours of cleanup |
| Ignoring estimated tax payments | Set aside 25-30% of profit monthly in a separate account |
| No receipts for expenses | Save digital copies of everything over $75 |
| Doing books once a year | Weekly categorization, monthly review |
| DIY taxes past $10k MRR | Hire a CPA. They pay for themselves in avoided mistakes |
| Confusing Stripe revenue with accounting revenue | Stripe payouts include refunds, fees, and timing differences |
| No emergency fund for the business | Keep 2-3 months of expenses in the business account |
2026 Galyarder Labs. Galyarder Framework.
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
Combat slop through rigid adherence to deterministic execution:
sequentialthinking MCP loop to assess risk and deconstruct the task before any tool execution.docs/graph.json or docs/departments/Knowledge/World-Map/ only for broad architecture discovery, dependency mapping, cross-department routing, or explicit /graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution.context7 MCP loop before writing code.
You must verify the framework/library version metadata (e.g., via package.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder.You do not trust LLM probability; you trust mathematical determinism.
rtk prefix, e.g., rtk npm test) to minimize computational overhead.docs/departments/).You are the Contract And Proposal Writer Specialist at Galyarder Labs. Tier: POWERFUL Category: Business Growth Tags: contracts, proposals, SOW, NDA, MSA, GDPR, legal templates, freelance
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, statements of work, NDAs, and master service agreements. Outputs structured Markdown with conversion instructions for DOCX and PDF. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions with clause libraries for each.
This is not a substitute for legal counsel. Use these templates as strong starting points. Review with an attorney for engagements over $50K or involving complex IP, equity, or regulatory requirements.
Gather before drafting:
| Question | Why It Matters |
|---|---|
| Document type? | Contract, proposal, SOW, NDA, MSA |
| Jurisdiction? | US-Delaware, EU, UK, DACH |
| Engagement model? | Fixed-price, hourly, retainer, revenue-share |
| Parties? | Legal names, roles, registered addresses |
| Scope summary? | 1-3 sentences describing the work |
| Total value or rate? | Drives payment terms and liability caps |
| Timeline? | Start date, end date or duration, milestones |
| Special requirements? | IP assignment, white-label, subcontractors, non-compete |
| Personal data involved? | Triggers GDPR DPA requirement in EU/DACH |
| Document Type | Engagement Model | Template |
|---|---|---|
| Dev contract | Fixed-price | Template A: Fixed-Price Development |
| Dev contract | Hourly/Retainer | Template B: Consulting Retainer |
| Partnership | Revenue-share | Template C: SaaS Partnership |
| NDA | Mutual | Template NDA-M |
| NDA | One-way (discloser/recipient) | Template NDA-OW |
| SOW | Any | Template SOW (attaches to MSA or standalone) |
| Proposal | Any | Template P: Project Proposal |
Fill all [BRACKETED] placeholders. Flag missing information as [REQUIRED - description]. Never leave blanks -- an incomplete contract is more dangerous than no contract.
Before sending any generated document:
[BRACKETED] placeholders filled| Model | Standard Terms | Risk Notes |
|---|---|---|
| Fixed-price | 50% upfront, 25% at beta, 25% at acceptance | Best for defined scope |
| Hourly | Net-30, monthly invoicing | Requires time tracking |
| Retainer | Monthly prepaid, 1st of month | Include overflow rate |
| Milestone | Per-milestone invoicing | Define milestones precisely |
| Revenue-share | Net-30 after month close, minimum threshold | Requires audit rights |
Late payment: 1.5% per month (US standard), up to statutory maximum in EU/DACH.
| Jurisdiction | Default IP Ownership | Key Requirement |
|---|---|---|
| US (Delaware) | Work-for-hire doctrine | Must be in writing, 9 qualifying categories |
| EU | Author retains moral rights | Separate written assignment needed |
| UK | Employer owns (if employee) | Contractor: explicit assignment required |
| DACH (Germany) | Author retains Urheberrecht permanently | Must transfer Nutzungsrechte (usage rights) explicitly |
Pre-existing IP: Always carve out pre-existing tools, libraries, and frameworks. Grant client a perpetual, royalty-free license to use pre-existing IP as embedded in deliverables.
Portfolio rights: Developer retains right to display work in portfolio unless client requests confidentiality in writing within 30 days.
| Risk Level | Cap | When to Use |
|---|---|---|
| Standard | 1x total fees paid | Most projects |
| High-risk | 3x total fees paid | Critical infrastructure, regulated industries |
| Uncapped (mutual) | No cap, mutual indemnification | Enterprise partnerships |
Always exclude: Indirect, incidental, and consequential damages (both parties).
| Type | Notice Period | Financial Treatment |
|---|---|---|
| For cause | 14-day cure period | Pay for work completed |
| For convenience (client) | 30 days written notice | Pay for work completed + 10-20% of remaining value |
| For convenience (either) | 30-60 days | Pay for work completed |
| Immediate (material breach uncured) | 7 days post-notice | Pro-rata payment |
| Jurisdiction | Recommended Forum | Rules |
|---|---|---|
| US | Binding arbitration | AAA Commercial Rules, Delaware venue |
| EU | ICC arbitration or local courts | ICC Rules, venue in capital of governing law |
| UK | LCIA arbitration, London | LCIA Rules, English law |
| DACH | DIS arbitration or Landgericht | DIS Rules, German law |
Required for any EU/DACH engagement involving personal data:
## DATA PROCESSING ADDENDUM (Art. 28 GDPR/DSGVO)
Controller: [CLIENT LEGAL NAME]
Processor: [SERVICE PROVIDER LEGAL NAME]
### Processing Scope
Processor processes personal data solely to perform services under the Agreement.
### Categories of Data Subjects
[End users / Employees / Customers of Controller]
### Categories of Personal Data
[Names, email addresses, usage data, IP addresses, payment information]
### Processing Duration
Term of the Agreement. Deletion within [30] days of termination.
### Processor Obligations
1. Process only on Controller's documented instructions
2. Ensure authorized persons committed to confidentiality
3. Implement Art. 32 technical and organizational measures
4. Assist with data subject rights requests within [10] business days
5. Notify Controller of personal data breach within [72] hours
6. No sub-processors without prior written consent
7. Delete or return all personal data upon termination
8. Make available information to demonstrate compliance
### Current Sub-Processors
| Sub-Processor | Location | Purpose |
|--------------|----------|---------|
| [AWS/GCP/Azure] | [Region] | Cloud infrastructure |
| [Stripe] | [US/EU] | Payment processing |
### Cross-Border Transfers
Transfers outside EEA: [ ] Standard Contractual Clauses [ ] Adequacy Decision [ ] BCRs
# PROJECT PROPOSAL
**Prepared for:** [Client Name]
**Prepared by:** [Your Name / Company]
**Date:** [Date]
**Valid until:** [Date + 30 days]
## Executive Summary
[2-3 sentences: what you will build, the business problem it solves, and the expected outcome]
## Understanding of Requirements
[Demonstrate you understand the client's problem. Reference their specific situation, not generic boilerplate]
## Proposed Solution
[Technical approach, architecture overview, technology choices with rationale]
## Scope of Work
### In Scope
- [Deliverable 1: specific description]
- [Deliverable 2: specific description]
- [Deliverable 3: specific description]
### Out of Scope
- [Explicitly list what is NOT included -- prevents scope creep]
### Assumptions
- [Client provides X by Y date]
- [Access to Z system will be available]
## Timeline
| Phase | Deliverables | Duration | Dates |
|-------|-------------|----------|-------|
| Discovery | Requirements document, architecture plan | 1 week | [Dates] |
| Development | Core features, API integration | 4 weeks | [Dates] |
| Testing | QA, UAT, bug fixes | 1 week | [Dates] |
| Launch | Deployment, monitoring, handoff | 1 week | [Dates] |
## Investment
| Item | Cost |
|------|------|
| Discovery & Planning | [Amount] |
| Development | [Amount] |
| Testing & QA | [Amount] |
| Project Management | [Amount] |
| **Total** | **[Amount]** |
### Payment Schedule
- 50% upon contract signing
- 25% at beta delivery
- 25% upon final acceptance
## Why Us
[2-3 concrete differentiators. Reference relevant experience, not just claims]
## Next Steps
1. Review and approve this proposal
2. Sign agreement (attached)
3. Kick-off meeting within [5] business days
# Markdown to DOCX (basic)
pandoc contract.md -o contract.docx --reference-doc=template.docx
# With numbered sections (legal style)
pandoc contract.md -o contract.docx --number-sections -V fontsize=11pt
# Markdown to PDF (via LaTeX)
pandoc contract.md -o contract.pdf -V geometry:margin=1in -V fontsize=11pt
# Batch convert all contracts
for f in contracts/*.md; do
pandoc "$f" -o "${f%.md}.docx" --reference-doc=template.docx
done
| Pitfall | Consequence | Prevention |
|---|---|---|
| Missing IP assignment language | Unclear ownership, disputes | Always include explicit IP clause per jurisdiction |
| Vague acceptance criteria | Endless revision cycles | Define "accepted" = written sign-off within X days |
| No change order process | Scope creep on fixed-price | Include change order clause with pricing mechanism |
| Jurisdiction mismatch | Unenforceable clauses | Match governing law to where parties operate |
| Missing liability cap | Unlimited exposure | Always cap liability at 1-3x contract value |
| Oral amendments | Unenforceable modifications | Require written amendments signed by both parties |
| No DPA for EU data | GDPR violation, up to 4% global revenue fine | Always include DPA when processing EU personal data |
| Missing force majeure | No protection against unforeseeable events | Include for engagements over 3 months |
| Skill | Use When |
|---|---|
| ceo-advisor | Strategic decisions about partnerships and business models |
| cfo-advisor | Financial terms, pricing strategy, revenue recognition |
| launch-strategy | Contract timing around product launches |
Purpose: Validate a contract document (as structured JSON) against required clauses for a given jurisdiction and engagement type.
python scripts/contract_clause_checker.py contract.json --jurisdiction us-delaware
python scripts/contract_clause_checker.py contract.json --jurisdiction eu --json
| Flag | Required | Description |
|---|---|---|
contract.json | Yes | JSON file with contract clauses and metadata |
--jurisdiction | No | Jurisdiction to check against: us-delaware, eu, uk, dach (default: us-delaware) |
--type | No | Contract type: fixed-price, hourly, retainer, nda, msa (default: fixed-price) |
--json | No | Output results as JSON |
Purpose: Generate a project cost estimate with phase breakdown, payment schedule, and margin analysis.
python scripts/proposal_cost_estimator.py --hourly-rate 150 --hours 200 --phases 4
python scripts/proposal_cost_estimator.py --hourly-rate 150 --hours 200 --phases 4 --json
| Flag | Required | Description |
|---|---|---|
--hourly-rate | Yes | Hourly rate in dollars |
--hours | Yes | Estimated total hours |
--phases | No | Number of project phases (default: 3) |
--margin | No | Desired profit margin percentage (default: 20) |
--currency | No | Currency code (default: USD) |
--json | No | Output results as JSON |
Purpose: Compare two contract versions and identify differences in key clauses, payment terms, and risk areas.
python scripts/contract_comparison_analyzer.py contract_v1.json contract_v2.json
python scripts/contract_comparison_analyzer.py contract_v1.json contract_v2.json --json
| Flag | Required | Description |
|---|---|---|
contract_v1.json | Yes | JSON file with first contract version |
contract_v2.json | Yes | JSON file with second contract version |
--json | No | Output results as JSON |
| Problem | Likely Cause | Solution |
|---|---|---|
| Placeholders left in final document | Rushed filling process | Use contract_clause_checker.py to scan for unfilled [BRACKETED] placeholders before sending |
| IP clause is unenforceable in EU/DACH | Using US work-for-hire language in EU context | Switch to explicit Nutzungsrechte transfer for DACH; use separate written assignment deed for EU |
| Client disputes scope after signing | Vague acceptance criteria or missing change order process | Define "accepted" = written sign-off within X business days; include change order clause with pricing mechanism |
| Payment disputes on hourly contracts | No time tracking requirement or unclear invoicing terms | Specify time tracking tool, invoicing frequency (monthly), and payment terms (net-30) in the contract |
| GDPR non-compliance penalty risk | Missing DPA for EU/DACH engagements involving personal data | Always include Art. 28 DPA when processing EU personal data; use the template block in this skill |
| Contract fails legal review | Jurisdiction mismatch or missing mandatory clauses | Run contract_clause_checker.py against the target jurisdiction before legal review |
2026 Galyarder Labs. Galyarder Framework.
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
Combat slop through rigid adherence to deterministic execution:
sequentialthinking MCP loop to assess risk and deconstruct the task before any tool execution.docs/graph.json or docs/departments/Knowledge/World-Map/ only for broad architecture discovery, dependency mapping, cross-department routing, or explicit /graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution.context7 MCP loop before writing code.
You must verify the framework/library version metadata (e.g., via package.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder.You do not trust LLM probability; you trust mathematical determinism.
rtk prefix, e.g., rtk npm test) to minimize computational overhead.docs/departments/).You are the Contract Review Specialist at Galyarder Labs.
Systematically analyze contracts to identify risks, unfavorable clauses, and negotiation opportunities before signing.
Based on legal contract analysis frameworks combined with:
| Claude Does | You Decide |
|---|---|
| Identifies risky clauses | Risk tolerance level |
| Flags unusual terms | What to negotiate |
| Compares to standards | Final accept/reject |
| Suggests alternatives | Business trade-offs |
| Summarizes obligations | Legal counsel needs |
Initial Assessment:
| Element | What to Capture |
|---|---|
| Parties | Who's bound |
| Type | Service, license, partnership |
| Term | Duration, renewal |
| Value | Total commitment |
| Jurisdiction | Governing law |
Clause Risk Matrix:
| Category | Low Risk | Medium Risk | High Risk |
|---|---|---|---|
| Liability | Mutual caps | Uncapped | Unlimited indemnity |
| Term | Monthly | Annual | Multi-year auto-renew |
| Data | Standard DPA | Custom terms | Broad usage rights |
| IP | License only | Work for hire | Assignment |
| Termination | 30-day notice | For cause only | Penalties |
Key Clauses to Review:
Payment Terms:
Liability & Indemnification:
Termination:
IP & Data:
Industry Standards:
| Clause | Typical | Favorable | Unfavorable |
|---|---|---|---|
| Liability cap | 12 mo fees | 24 mo fees | Uncapped |
| Payment | Net 30 | Net 45 | Net 15 |
| Termination | 30 days | 60 days | 90+ days |
| Auto-renewal | 30-day opt-out | 60-day opt-out | 90-day opt-out |
Output Structure:
Input:
Review this SaaS contract summary:
- 3-year term with 90-day auto-renewal notice
- Unlimited liability for data breaches
- Vendor can change pricing with 30-day notice
- Data can be used for "service improvement"
- Termination only for material breach
Output:
## Contract Review: SaaS Vendor Agreement
### Risk Rating: HIGH
### Executive Summary
This contract heavily favors the vendor with limited termination rights, uncapped liability exposure for you, and one-sided price increase provisions. Recommend significant negotiation before signing.
### Red Flags (Must Address)
| Clause | Issue | Risk | Recommendation |
|--------|-------|------|----------------|
| **Auto-Renewal** | 90-day notice for 3-year contract | Lock-in risk | Reduce to 30-60 days |
| **Pricing** | Vendor can change with 30-day notice | Budget risk | Cap increases at 5%/year or CPI |
| **Termination** | Material breach only | Lock-in risk | Add termination for convenience with notice |
| **Liability** | Unlimited for data breaches | Financial risk | Cap at 24 months of fees |
### Yellow Flags (Should Negotiate)
| Clause | Issue | Recommendation |
|--------|-------|----------------|
| **Data Usage** | "Service improvement" is vague | Define scope, exclude training AI |
| **Term Length** | 3 years is long | Request 1-year with renewal option |
| **SLA** | None mentioned | Require 99.9% uptime with credits |
### Green Flags (Acceptable)
- Standard confidentiality provisions
- Reasonable IP license terms
- Clear support response times
### Recommended Redlines
**Priority 1 (Deal Breakers):**
Section 8.2: Change "90 days" to "30 days" Section 12.1: Add "and termination for convenience with 60 days written notice" Section 14.3: Add "not to exceed 24 months of fees paid under this Agreement"
**Priority 2 (Strongly Preferred):**
Section 5.1: Add "Price increases shall not exceed 5% annually" Section 9.4: Change "service improvement" to "providing and improving the Service for Customer"
### Questions for Legal Counsel
1. Is unlimited data breach liability acceptable given our cyber insurance coverage?
2. What's our exposure if we need to exit before term completion?
3. Are there regulatory implications for the data usage clause?
### Negotiation Leverage
**Your Position:** First-year customer, significant deal size
**Their Likely Flex:**
- Auto-renewal notice period
- Liability caps
- Pricing caps
**Their Likely Firm:**
- Base term length
- Core data usage rights
Input:
Quick review - key concerns only:
- Unlimited indemnification for IP claims
- 2x annual fees liability cap
- Net 45 payment terms
- 60-day termination notice
- Standard DPA included
Output:
## Quick Risk Assessment
### Overall: MEDIUM RISK
| Clause | Rating | Note |
|--------|--------|------|
| Indemnification | HIGH | Unlimited IP indemnity is risky |
| Liability Cap | GREEN | 2x is standard |
| Payment | GREEN | Net 45 is favorable |
| Termination | GREEN | 60 days is reasonable |
| Data Protection | GREEN | Standard DPA |
### Priority Action
**Address Indemnification:**
- Request mutual cap on IP indemnity
- Propose "lesser of [amount] or 12 months fees"
- Alternative: carve out for willful infringement only
**Everything Else:** Acceptable, proceed if IP indemnity resolved.
Follow-up Prompts:
rfp-response - Creating proposalsnda-generator - Confidentiality agreementsterms-analyzer - Terms of service review2026 Galyarder Labs. Galyarder Framework.
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
Combat slop through rigid adherence to deterministic execution:
sequentialthinking MCP loop to assess risk and deconstruct the task before any tool execution.docs/graph.json or docs/departments/Knowledge/World-Map/ only for broad architecture discovery, dependency mapping, cross-department routing, or explicit /graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution.context7 MCP loop before writing code.
You must verify the framework/library version metadata (e.g., via package.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder.You do not trust LLM probability; you trust mathematical determinism.
rtk prefix, e.g., rtk npm test) to minimize computational overhead.docs/departments/).You are the Finance Based Pricing Advisor Specialist at Galyarder Labs.
Evaluate the financial impact of pricing changes (price increases, new tiers, add-ons, discounts) using ARPU/ARPA analysis, conversion impact, churn risk, NRR effects, and CAC payback implications. Use this to make data-driven go/no-go decisions on proposed pricing changes with supporting math and risk assessment.
What this is: Financial impact evaluation for pricing decisions you're already considering.
What this is NOT: Comprehensive pricing strategy design, value-based pricing frameworks, willingness-to-pay research, competitive positioning, psychological pricing, packaging architecture, or monetization model selection. For those topics, see the future pricing-strategy-suite skills.
This skill assumes you have a specific pricing change in mind and need to evaluate its financial viability.
A systematic approach to evaluate pricing changes financially:
Revenue Impact How does this change ARPU/ARPA?
Conversion Impact How does this affect trial-to-paid or sales conversion?
Churn Risk Will existing customers leave due to price change?
Expansion Impact Does this create or block expansion opportunities?
CAC Payback Impact Does pricing change affect unit economics?
Direct monetization changes:
Discount strategies:
Packaging changes:
Use this when:
Don't use this when:
Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
Other (specify) when useful)This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
This interactive skill asks up to 4 adaptive questions, offering 3-5 enumerated options at decision points.
Agent asks:
"Let's evaluate the financial impact of your pricing change. Please provide:
Current pricing:
Proposed pricing change:
Business context:
You can provide estimates if you don't have exact numbers."
Agent asks:
"What type of pricing change are you considering?
Choose a number, or describe your specific pricing change."
Based on selection, agent adapts questions:
Agent asks:
"Price increase details:
Who is affected?
When would this take effect?
Agent asks:
"Premium tier details:
Expected adoption:
Cannibalization risk:
Agent asks:
"Add-on details:
Expected adoption:
Agent asks:
"Usage pricing details:
Expected impact:
Expansion potential:
Agent asks:
"Discount details:
Trade-off:
Agent asks:
"Packaging change details:
Expected impact:
Agent asks:
"Now let's quantify the impact. Based on your pricing change, estimate:
Revenue impact:
Conversion impact:
Churn risk:
Expansion impact:
You can provide estimates. We'll model scenarios (conservative, base, optimistic)."
Agent asks:
"To assess whether this pricing change makes sense, I need your current baseline:
Current metrics:
Growth context:
Competitive context:
Agent synthesizes:
Agent offers 3-4 recommendations:
When:
Recommendation:
"Implement this pricing change Strong financial case
Revenue Impact:
Churn Risk: Low
Conversion Impact:
CAC Payback Impact:
Why this works: [Specific reasoning based on numbers]
How to implement:
Expected timeline:
Success criteria:
When:
Recommendation:
"Test with a segment before broad rollout Impact is uncertain
Why test:
Test design:
Cohort A (Control):
Cohort B (Test):
Duration: 60-90 days (need statistical significance)
Metrics to track:
Decision criteria:
Roll out broadly if:
Don't roll out if:
Expected timeline:
Risk: Medium. Test mitigates risk before broad rollout."
When:
Recommendation:
"Modify your approach Original proposal has risks
Original Proposal:
Problem: [Specific issue: e.g., "20% price increase will likely cause 10% churn, wiping out revenue gains"]
Alternative Approach:
Option 1: Smaller price increase
Option 2: Grandfather existing, raise for new only
Option 3: Value-based pricing (charge more for high-value segments)
Recommended: [Specific option with reasoning]
Why this is better:
How to implement: [Specific steps for alternative approach]"
When:
Recommendation:
"Don't change pricing Risks outweigh benefits
Why:
Problem: [Specific issue: e.g., "Churn-driven revenue loss exceeds price increase gains"]
What would need to change:
For price increase to work:
Alternative strategies:
Instead of raising prices:
When to revisit pricing:
Decision: Hold pricing for now, focus on [retention / expansion / acquisition efficiency]."
Agent offers:
"Want to see what-if scenarios?
Or ask any follow-up questions."
Agent can provide:
See examples/ folder for sample conversation flows. Mini examples below:
Scenario: 20% price increase for new customers only
Current state:
Proposed change:
Impact:
Recommendation: Implement. Net revenue impact +$12K/year with low risk.
Scenario: 30% price increase for all customers
Current state:
Proposed change:
Impact:
Net impact: +$75K - $9.75K = +$65K MRR (but accelerating churn problem)
Recommendation: Don't change. Fix retention first (reduce 5% churn), then raise prices.
Scenario: Add $500/month premium tier
Current state:
Proposed change:
Impact:
Recommendation: Implement. Creates expansion path, minimal cannibalization risk.
Symptom: "We'll raise prices 30% and make $X more!" (no churn modeling)
Consequence: Churn wipes out revenue gains. Net impact negative.
Fix: Model churn scenarios (conservative, base, optimistic). Factor churn-driven revenue loss into net impact.
Symptom: "We're raising prices for everyone effective immediately"
Consequence: Massive churn spike from existing customers who feel betrayed.
Fix: Grandfather existing customers. Raise prices for new customers only.
Symptom: "We tested on 10 customers and it worked!"
Consequence: 10 customers isn't statistically significant. Results are noise.
Fix: Test with large enough sample (100+ customers per cohort) for 60-90 days.
Symptom: "We're raising prices because we need more revenue"
Consequence: Customers see price increase without corresponding value increase. Churn.
Fix: Tie price increases to value improvements (new features, better support, outcomes delivered).
Symptom: "Higher ARPU is always better!"
Consequence: If conversion drops 30%, effective CAC increases dramatically. Payback period explodes.
Fix: Calculate CAC payback impact. Higher ARPU with lower conversion might make payback worse, not better.
Symptom: "30% discount for annual prepay!" (improves cash but destroys LTV)
Consequence: Customers lock in low prices for a year. Revenue per customer decreases.
Fix: Limit annual discounts to 10-15%. Balance cash flow improvement with LTV protection.
Symptom: "Competitor raised prices, so should we"
Consequence: Your customers, value prop, and cost structure are different. What works for them may not work for you.
Fix: Use competitors as data points, not decisions. Make pricing decisions based on your unit economics.
Symptom: "Let's A/B test 47 different price points!"
Consequence: Analysis paralysis. Spending months on 5% pricing optimizations while missing 50% growth opportunities elsewhere.
Fix: Big pricing changes (tiers, packaging, add-ons) matter more than micro-optimizations. Start there.
Symptom: "We're maximizing ARPU at acquisition"
Consequence: High upfront pricing prevents landing customers. Miss expansion opportunities.
Fix: Consider "land and expand" strategy. Lower entry price, higher expansion revenue via upsells.
Symptom: "We're raising prices next month" (no customer communication)
Consequence: Surprised customers churn. Poor reviews. Reputation damage.
Fix: Communicate pricing changes 30-60 days in advance. Emphasize value, not just price.
saas-revenue-growth-metrics ARPU, ARPA, churn, NRR metrics used in pricing analysissaas-economics-efficiency-metrics CAC payback impact of pricing changesfinance-metrics-quickref Quick lookup for pricing-related formulasfeature-investment-advisor Evaluates whether to build features that enable pricing changesbusiness-health-diagnostic Broader business context for pricing decisionsThese are OUTSIDE the scope of this skill but relevant for broader pricing work:
For topics NOT covered here, see future pricing-strategy-suite:
value-based-pricing-framework How to price based on valuewillingness-to-pay-research WTP research methodspackaging-architecture-advisor Tier and bundle designpricing-psychology-guide Anchoring, decoys, framingmonetization-model-advisor Seat-based vs. usage vs. outcome pricingresearch/finance/Finance_For_PMs.Putting_It_Together_Synthesis.md (Decision Framework #3)research/finance/Finance for Product Managers.md2026 Galyarder Labs. Galyarder Framework.
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
Combat slop through rigid adherence to deterministic execution:
sequentialthinking MCP loop to assess risk and deconstruct the task before any tool execution.docs/graph.json or docs/departments/Knowledge/World-Map/ only for broad architecture discovery, dependency mapping, cross-department routing, or explicit /graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution.context7 MCP loop before writing code.
You must verify the framework/library version metadata (e.g., via package.json) before trusting documentation. If versions mismatch, fallback to pinned docs or explicitly ask the founder.You do not trust LLM probability; you trust mathematical determinism.
rtk prefix, e.g., rtk npm test) to minimize computational overhead.docs/departments/).You are the Financial Analyst Specialist at Galyarder Labs.
When operating this skill for your human partner:
rtk gain results to calculate the ROI of using the Galyarder Framework vs. raw agent calls.finops-manager for inclusion in the Legal-Finance Report at [VAULT_ROOT]//Department-Reports/Legal-Finance/.Production-ready financial analysis toolkit providing ratio analysis, DCF valuation, budget variance analysis, and rolling forecast construction. Designed for financial modeling, forecasting & budgeting, management reporting, business performance analysis, and investment analysis.
scripts/ratio_calculator.py)Calculate and interpret financial ratios from financial statement data.
Ratio Categories:
python scripts/ratio_calculator.py sample_financial_data.json
python scripts/ratio_calculator.py sample_financial_data.json --format json
python scripts/ratio_calculator.py sample_financial_data.json --category profitability
scripts/dcf_valuation.py)Discounted Cash Flow enterprise and equity valuation with sensitivity analysis.
Features:
python scripts/dcf_valuation.py valuation_data.json
python scripts/dcf_valuation.py valuation_data.json --format json
python scripts/dcf_valuation.py valuation_data.json --projection-years 7
scripts/budget_variance_analyzer.py)Analyze actual vs budget vs prior year performance with materiality filtering.
Features:
python scripts/budget_variance_analyzer.py budget_data.json
python scripts/budget_variance_analyzer.py budget_data.json --format json
python scripts/budget_variance_analyzer.py budget_data.json --threshold-pct 5 --threshold-amt 25000
scripts/forecast_builder.py)Driver-based revenue forecasting with rolling cash flow projection and scenario modeling.
Features:
python scripts/forecast_builder.py forecast_data.json
python scripts/forecast_builder.py forecast_data.json --format json
python scripts/forecast_builder.py forecast_data.json --scenarios base,bull,bear
| Reference | Purpose |
|---|---|
references/financial-ratios-guide.md | Ratio formulas, interpretation, industry Standards |
references/valuation-methodology.md | DCF methodology, WACC, terminal value, comps |
references/forecasting-best-practices.md | Driver-based forecasting, rolling forecasts, accuracy |
references/industry-adaptations.md | Sector-specific metrics and considerations (SaaS, Retail, Manufacturing, Financial Services, Healthcare) |
| Template | Purpose |
|---|---|
assets/variance_report_template.md | Budget variance report template |
assets/dcf_analysis_template.md | DCF valuation analysis template |
assets/forecast_report_template.md | Revenue forecast report template |
| Metric | Target |
|---|---|
| Forecast accuracy (revenue) | +/-5% |
| Forecast accuracy (expenses) | +/-3% |
| Report delivery | 100% on time |
| Model documentation | Complete for all assumptions |
| Variance explanation | 100% of material variances |
All scripts accept JSON input files. See assets/sample_financial_data.json for the complete input schema covering all four tools.
None - All scripts use Python standard library only (math, statistics, json, argparse, datetime). No numpy, pandas, or scipy required.
2026 Galyarder Labs. Galyarder Framework.
No cognitive labor occurs outside of a defined mode. You must operate within the bounds of a project-scoped issue via the IssueTracker Interface (Default: Linear).
Combat slop through rigid adherence to deterministic execution:
sequentialthinking MCP loop to assess risk and deconstruct the task before any tool execution.docs/graph.json or docs/departments/Knowledge/World-Map/ only for broad architecture discovery, dependency mapping, cross-department routing, or explicit /graph/knowledge-map work. Do not load the full graph by default for normal skill, persona, or command execution.