Add dev_commit.sh helper and no-emoji mandate
This commit is contained in:
@@ -0,0 +1,200 @@
|
||||
KEY ELEMENTS EXTRACTED FROM LANDPROZ CONTRACTS
|
||||
================================================
|
||||
Date: October 29, 2025
|
||||
Purpose: Template elements for HomeProz WordPress website contract
|
||||
|
||||
|
||||
BUSINESS IDENTITY
|
||||
-----------------
|
||||
Current legal name: Hanson.xyz (S-Corporation as of 2024, was Hansonxyz LLC)
|
||||
State: Minnesota
|
||||
Standard hourly rate: $175/hour (15-minute increments)
|
||||
Change request rate: $250/hour (used in contracts)
|
||||
|
||||
|
||||
CONTRACT STRUCTURE OPTIONS
|
||||
---------------------------
|
||||
Option 1: Separate Proposal + Statement of Work (2023 auction project)
|
||||
- Proposal: Executive summary, objectives, implementation, phases, timeline, conclusion
|
||||
- SOW: Legal contract language with scope, payment, IP, warranty, governing law
|
||||
|
||||
Option 2: Combined Proposal with Legal Sections (2025 whitelabel project)
|
||||
- Single document with deliverables, timeline, budget, then legal clauses
|
||||
- More concise, better for smaller projects
|
||||
|
||||
|
||||
PAYMENT STRUCTURES OBSERVED
|
||||
----------------------------
|
||||
1. Flat fee with upfront payment
|
||||
Example: $36,000 total, $12,000 upfront, $24,000 on completion
|
||||
|
||||
2. Flat fee invoiced on delivery with net payment terms
|
||||
Example: $10,500 invoiced on delivery date with net 30 terms
|
||||
|
||||
3. Hourly billing (not seen in references, but mentioned as standard rate)
|
||||
|
||||
For 40-hour project:
|
||||
- 40 hours × $175/hour = $7,000 flat fee
|
||||
- Could do $2,500 upfront, $4,500 on completion
|
||||
- Or invoice full amount on delivery with net 30
|
||||
|
||||
|
||||
STANDARD PROJECT PHASES
|
||||
------------------------
|
||||
1. Design/Planning
|
||||
- Requirements gathering
|
||||
- Wireframes or mockups
|
||||
- Client approval before development
|
||||
|
||||
2. Development
|
||||
- Implementation of features
|
||||
- Progress updates
|
||||
- Staging environment for review
|
||||
|
||||
3. Testing and Client Acceptance
|
||||
- QA testing
|
||||
- Client feedback
|
||||
- Bug fixes
|
||||
- Final approval
|
||||
|
||||
4. Launch/Deployment
|
||||
- Go-live to production
|
||||
- Final testing
|
||||
|
||||
5. Warranty Period
|
||||
- 60 days standard
|
||||
- Free fixes for promised functionality
|
||||
- Additional work quoted separately
|
||||
|
||||
|
||||
TIMELINE APPROACH
|
||||
-----------------
|
||||
- Provide estimated hours for project
|
||||
- Calendar timeline (weeks/months)
|
||||
- Key milestone dates
|
||||
- Language about unforeseen delays and right to terminate
|
||||
|
||||
Example for 40-hour project:
|
||||
- 2-4 week timeline depending on complexity and client feedback
|
||||
- Weekly check-ins
|
||||
- Specific dates for design approval, development completion, launch
|
||||
|
||||
|
||||
SCOPE DEFINITION BEST PRACTICES
|
||||
--------------------------------
|
||||
- Clear deliverables list
|
||||
- Explicit exclusions ("This project excludes...")
|
||||
- Responsive design statement
|
||||
- Browser compatibility
|
||||
- What client must provide (content, images, etc.)
|
||||
- Change request process
|
||||
|
||||
|
||||
LEGAL CLAUSES (STANDARD IN ALL CONTRACTS)
|
||||
------------------------------------------
|
||||
|
||||
1. Independent Contractor Status
|
||||
"Hanson.xyz shall perform all work under this agreement as an independent
|
||||
contractor. Nothing herein shall be construed to create a partnership, joint
|
||||
venture, or employer-employee relationship between the parties."
|
||||
|
||||
2. Governing Law and Jurisdiction
|
||||
"This agreement shall be governed by and construed in accordance with the
|
||||
laws of the State of Minnesota. Any legal action or proceeding arising under
|
||||
this agreement shall be brought exclusively in the courts located within the
|
||||
State of Minnesota."
|
||||
|
||||
3. Intellectual Property and Work Product
|
||||
- Client owns all work product upon full payment
|
||||
- Developer grants perpetual license to use
|
||||
- Developer retains rights to pre-existing tools/frameworks
|
||||
- Consultant Tools provision for reusable code libraries
|
||||
|
||||
4. Warranty
|
||||
"The Developer will guarantee their services for 60 days after the completion
|
||||
of the project. During this warranty period, the Developer will provide any
|
||||
necessary fixes to functionality provided within the 'Scope of work' at no
|
||||
additional cost. After the expiration of the warranty period, any additional
|
||||
changes, modifications, or support for the functionality provided will be
|
||||
quoted separately from this agreement."
|
||||
|
||||
5. Limitation of Liability
|
||||
"Hanson.xyz's liability for any claim arising out of this agreement shall not
|
||||
exceed the total compensation paid under this agreement. In no event shall
|
||||
Hanson.xyz be liable for any consequential, incidental, special, or punitive
|
||||
damages, including lost profits or business interruption."
|
||||
|
||||
6. Indemnification
|
||||
"Each party shall indemnify and hold the other harmless from any third-party
|
||||
claims resulting from its own gross negligence or intentional misconduct in
|
||||
connection with this agreement."
|
||||
|
||||
7. Change Requests
|
||||
"After the scope of work has been agreed upon, any changes requested by the
|
||||
Client to the scope of work must be approved in writing by both parties before
|
||||
they can be implemented. The Developer will provide a quote at the rate of
|
||||
$250 per hour for the work, and the Client will pay the additional fee as
|
||||
specified in the quote. The Developer will not begin any additional work until
|
||||
the Client has approved the quote in writing."
|
||||
|
||||
8. Confidentiality
|
||||
"Both parties agree to keep the details of this contract and the project
|
||||
confidential, except as otherwise agreed in writing. Any information or
|
||||
materials shared by the Client with the Developer for the purposes of this
|
||||
project will be treated as confidential and will not be disclosed to any
|
||||
third party without the prior written consent of the disclosing party. The
|
||||
Client grants the Developer the right to showcase the completed project
|
||||
within their portfolio, subject to the Client's approval of the final product
|
||||
and any necessary confidentiality agreement."
|
||||
|
||||
9. Entire Agreement and Modifications
|
||||
"This document represents the full and complete agreement between the parties.
|
||||
Any modifications or amendments must be made in writing and signed by both
|
||||
parties."
|
||||
|
||||
10. Severability
|
||||
"If any provision of this agreement is found to be invalid or unenforceable,
|
||||
the remaining provisions shall continue in full force and effect."
|
||||
|
||||
11. Delivery Timeline Disclaimer
|
||||
"The developer will make every reasonable effort to deliver the project
|
||||
within the timeline specified. In the event of unforeseen delays, the client
|
||||
agrees not to hold the developer liable for exceeding the estimated delivery
|
||||
schedule. However, if the project is not delivered within a reasonable
|
||||
timeframe, the client reserves the right to terminate this agreement at
|
||||
their discretion."
|
||||
|
||||
|
||||
SIGNATURE BLOCK
|
||||
---------------
|
||||
"IN WITNESS WHEREOF, the parties have executed this Agreement:"
|
||||
|
||||
[Space for signatures and dates]
|
||||
|
||||
|
||||
WORDPRESS-SPECIFIC CONSIDERATIONS
|
||||
----------------------------------
|
||||
From whitelabel proposal:
|
||||
- WordPress plugin development mentioned
|
||||
- Theme customization
|
||||
- Responsive design
|
||||
- Mobile compatibility
|
||||
- Integration with existing WordPress infrastructure
|
||||
|
||||
Typical WordPress deliverables:
|
||||
- Custom theme or child theme
|
||||
- Plugin customization/development
|
||||
- Content migration
|
||||
- Training/documentation
|
||||
- Hosting setup (if applicable)
|
||||
|
||||
|
||||
NOTES FOR HOMEPROZ CONTRACT
|
||||
----------------------------
|
||||
- Use combined proposal format (simpler, more appropriate for 40-hour project)
|
||||
- Structure: Project description → Deliverables → Timeline/Budget → Legal clauses
|
||||
- Keep all standard legal clauses
|
||||
- 60-day warranty
|
||||
- Change requests at $250/hour
|
||||
- Payment structure TBD (need client info)
|
||||
- Specific deliverables TBD (need project details)
|
||||
Reference in New Issue
Block a user