Add dev_commit.sh helper and no-emoji mandate
This commit is contained in:
Hanson.xyz Dev
Binary file not shown.
Binary file not shown.
@@ -0,0 +1,389 @@
|
||||
HOMEPROZ CONTRACT AT-A-GLANCE
|
||||
==============================
|
||||
|
||||
PROJECT: WordPress Real Estate Website with Property Listing System
|
||||
CLIENT: HomeProz (startup housing division)
|
||||
DEVELOPER: Hanson.xyz
|
||||
|
||||
|
||||
QUICK SUMMARY
|
||||
=============
|
||||
|
||||
WHAT: Custom WordPress website with Advanced Custom Fields property listing
|
||||
system, styled to HomeProz brand, supporting both MLS and custom listings
|
||||
|
||||
HOW LONG: 1 week of active development, launching 4-5 weeks from contract signing
|
||||
(3-4 week queue + 1 week development)
|
||||
|
||||
HOW MUCH: $6,600 first year total
|
||||
- $6,000 development (one-time)
|
||||
- $600 managed hosting (annual, ongoing)
|
||||
|
||||
|
||||
DELIVERABLES CHECKLIST
|
||||
======================
|
||||
|
||||
Design & Planning:
|
||||
□ Design consultation based on HomeProz branding
|
||||
□ Theme selection and customization planning
|
||||
□ Property listing layout and structure
|
||||
□ ACF field structure planning
|
||||
|
||||
WordPress Development:
|
||||
□ Custom/child theme based on HomeProz design
|
||||
□ Responsive design (mobile, tablet, desktop)
|
||||
□ Homepage with property showcase
|
||||
□ Property listing pages with detailed fields
|
||||
□ Property search and filtering
|
||||
□ Individual property detail pages
|
||||
□ About/company page
|
||||
□ Contact page with form
|
||||
□ Browser compatibility testing
|
||||
□ Performance optimization
|
||||
□ Basic SEO implementation
|
||||
|
||||
ACF Implementation:
|
||||
□ ACF Pro plugin installation
|
||||
□ Custom field groups for properties
|
||||
□ Backend interface for property entry
|
||||
□ Field validation and configuration
|
||||
□ MLS number field
|
||||
|
||||
Additional Services:
|
||||
□ MLS integration planning (manual entry)
|
||||
□ Email migration support (up to 2 hours)
|
||||
□ Managed hosting setup
|
||||
□ SSL certificate installation
|
||||
□ Security configuration
|
||||
□ Backup system setup
|
||||
□ Staging environment
|
||||
|
||||
Training & Docs:
|
||||
□ 1-2 hour training session
|
||||
□ Written documentation
|
||||
□ Property listing workflow guide
|
||||
|
||||
Testing & Launch:
|
||||
□ QA testing
|
||||
□ Client review and revisions
|
||||
□ Production deployment
|
||||
□ Post-launch verification
|
||||
|
||||
|
||||
PRICING BREAKDOWN
|
||||
==================
|
||||
|
||||
DEVELOPMENT (ONE-TIME):
|
||||
Website development: $6,000
|
||||
Payment: $2,000 upfront
|
||||
$4,000 on completion
|
||||
|
||||
HOSTING (ANNUAL):
|
||||
Managed WordPress hosting: $600/year
|
||||
Includes: hosting, backups, security, updates, support (2 hrs/month)
|
||||
Payment: $600 at launch
|
||||
$600 annually on anniversary
|
||||
|
||||
FIRST YEAR TOTAL: $6,600
|
||||
|
||||
ONGOING YEARS: $600/year (hosting only)
|
||||
|
||||
|
||||
OPTIONAL ADD-ONS (Client pays separately):
|
||||
Northstar MLS: $100 setup + $55/month = $760/year
|
||||
Google Workspace: ~$6-12/user/month = $72-144/year
|
||||
Full IDX integration: $2,000-3,000+ (if desired later)
|
||||
|
||||
|
||||
TIMELINE
|
||||
========
|
||||
|
||||
Contract Signing: [DATE]
|
||||
↓
|
||||
3-4 week queue (completing current projects)
|
||||
↓
|
||||
Development Start: [DATE]
|
||||
↓
|
||||
1 week active development
|
||||
↓
|
||||
Client Review: [DATE]
|
||||
↓
|
||||
Revisions & Testing: 2-3 days
|
||||
↓
|
||||
Launch: [DATE] (~4-5 weeks from signing)
|
||||
↓
|
||||
60-day warranty period
|
||||
↓
|
||||
Ongoing hosting & support
|
||||
|
||||
|
||||
SCOPE BOUNDARIES
|
||||
================
|
||||
|
||||
INCLUDED:
|
||||
✓ WordPress theme customization
|
||||
✓ Advanced Custom Fields property system
|
||||
✓ MLS number field (manual entry)
|
||||
✓ Property search/filtering
|
||||
✓ Email migration help (2 hours)
|
||||
✓ Managed hosting setup
|
||||
✓ Training and documentation
|
||||
✓ 60-day warranty on functionality
|
||||
|
||||
EXCLUDED:
|
||||
✗ Full automated IDX MLS integration
|
||||
✗ E-commerce/payment processing
|
||||
✗ Content writing/copywriting
|
||||
✗ Logo design/branding creation
|
||||
✗ Professional photography
|
||||
✗ Custom mortgage calculators
|
||||
✗ Virtual tours/3D walkthroughs
|
||||
✗ CRM integration (Salesforce, etc.)
|
||||
✗ Ongoing MLS subscription fees
|
||||
✗ Google Workspace subscription fees
|
||||
|
||||
CHANGE ORDERS: $250/hour for additions beyond scope
|
||||
|
||||
|
||||
PAYMENT SCHEDULE
|
||||
================
|
||||
|
||||
Upon Contract Signing:
|
||||
Invoice: $2,000 (reserves development timeline)
|
||||
Due: Immediately
|
||||
|
||||
Upon Launch/Delivery:
|
||||
Invoice: $4,000 (development completion)
|
||||
$600 (first year hosting)
|
||||
Total: $4,600
|
||||
Due: Upon receipt (or within agreed terms)
|
||||
|
||||
Annually on Anniversary:
|
||||
Invoice: $600 (hosting renewal)
|
||||
Due: Net 15 days
|
||||
|
||||
|
||||
CLIENT MUST PROVIDE
|
||||
===================
|
||||
|
||||
Before Development:
|
||||
□ Logo and branding assets
|
||||
□ Company/about content text
|
||||
□ Property data for testing
|
||||
□ GoDaddy account access
|
||||
□ Design preferences/inspiration
|
||||
|
||||
During Development:
|
||||
□ Timely feedback (within 5 business days)
|
||||
□ Content for all pages
|
||||
□ Property photos and descriptions
|
||||
□ Email account access (if migrating)
|
||||
□ Decision-making authority
|
||||
|
||||
For Optional Services:
|
||||
□ Northstar MLS account setup (if using MLS)
|
||||
□ Google Workspace account setup (if migrating email)
|
||||
|
||||
|
||||
WARRANTY & SUPPORT
|
||||
==================
|
||||
|
||||
Warranty (60 days from launch):
|
||||
- Free fixes for bugs in custom code
|
||||
- Free fixes for functionality not working as designed
|
||||
- Does NOT cover: changes made by client, third-party issues,
|
||||
new features, hosting/server issues
|
||||
|
||||
After Warranty:
|
||||
- Ongoing hosting support: 2 hours/month included in hosting fee
|
||||
- Additional support: $175/hour
|
||||
- Hosting issues: covered under hosting agreement
|
||||
- New features: quoted separately
|
||||
|
||||
|
||||
LEGAL HIGHLIGHTS
|
||||
================
|
||||
|
||||
Governing Law: Minnesota
|
||||
Liability Cap: Total compensation paid
|
||||
IP Ownership: Client owns all work product upon payment
|
||||
Developer Tools: Developer retains rights to reusable frameworks/code
|
||||
Confidentiality: Both parties agree to keep details confidential
|
||||
Portfolio Rights: Developer may showcase with client approval
|
||||
Termination: Either party with 15 days notice for material breach
|
||||
Change Orders: Must be approved in writing by both parties
|
||||
|
||||
|
||||
HOSTING DETAILS
|
||||
===============
|
||||
|
||||
Included in $600/year managed hosting:
|
||||
- High-performance WordPress hosting
|
||||
- Daily automated backups (30-day retention)
|
||||
- Security monitoring and malware scanning
|
||||
- WordPress core/theme/plugin updates
|
||||
- SSL certificate management
|
||||
- Server maintenance
|
||||
- Staging environment
|
||||
- Technical support (up to 2 hours/month)
|
||||
- 99.9% uptime guarantee
|
||||
|
||||
Service Terms:
|
||||
- 1 year minimum commitment
|
||||
- Auto-renewal annually
|
||||
- 30 days notice to cancel
|
||||
- Migration assistance available if terminating (billed hourly)
|
||||
|
||||
|
||||
CONTACT INFORMATION
|
||||
===================
|
||||
|
||||
Developer:
|
||||
Hanson.xyz
|
||||
Brian Hanson
|
||||
State: Minnesota
|
||||
Rate: $175/hour standard, $250/hour for change orders
|
||||
Email: [INSERT]
|
||||
Phone: [INSERT]
|
||||
|
||||
Client:
|
||||
HomeProz
|
||||
Contact: Dayna Gottberg
|
||||
Legal Entity: [TO BE CONFIRMED]
|
||||
Email: [INSERT]
|
||||
Phone: [INSERT]
|
||||
|
||||
|
||||
CRITICAL QUESTIONS TO RESOLVE
|
||||
==============================
|
||||
|
||||
Before contract finalization, confirm:
|
||||
|
||||
1. [ ] Is $6,600 first year budget acceptable?
|
||||
2. [ ] Is $2,000 upfront payment feasible?
|
||||
3. [ ] Can client wait 3-4 weeks for development to start?
|
||||
4. [ ] Does HomeProz have logo/branding assets ready?
|
||||
5. [ ] Is manual MLS entry sufficient or need full IDX?
|
||||
6. [ ] How many email accounts need migration?
|
||||
7. [ ] What is exact legal business entity name?
|
||||
8. [ ] Annual or monthly hosting billing preference?
|
||||
9. [ ] Who purchases ACF Pro license ($49/year)?
|
||||
10. [ ] Are ongoing costs ($600-2,000/year) sustainable?
|
||||
|
||||
|
||||
DECISION TREE
|
||||
=============
|
||||
|
||||
Budget OK?
|
||||
├─ YES → Proceed with full scope as drafted
|
||||
└─ NO → Offer alternatives:
|
||||
- Phased approach (basic site first)
|
||||
- Payment plan ($500/month x 12)
|
||||
- Reduced scope (fewer features)
|
||||
- Template-based site ($3,500)
|
||||
|
||||
Timeline OK (3-4 week wait)?
|
||||
├─ YES → Proceed as scheduled
|
||||
└─ NO → Offer alternatives:
|
||||
- Rush fee +20% ($1,200) for immediate start
|
||||
- Reduce scope for faster launch
|
||||
- Defer project until schedule opens
|
||||
|
||||
MLS Integration?
|
||||
├─ Manual entry only → Included in current scope
|
||||
├─ IDX property display → +$2,000-3,000 additional
|
||||
├─ Full IDX database → +$5,000-10,000 additional
|
||||
└─ No MLS → Remove MLS-related deliverables
|
||||
|
||||
Email Migration?
|
||||
├─ Simple (1-3 accounts) → 2 hours likely sufficient
|
||||
├─ Complex (5+ accounts) → Quote additional time
|
||||
└─ Client handles → Remove from scope
|
||||
|
||||
|
||||
SUCCESS METRICS
|
||||
===============
|
||||
|
||||
Project is successful if:
|
||||
✓ Launched within 4-5 weeks of contract signing
|
||||
✓ HomeProz staff can easily add/manage property listings
|
||||
✓ Properties display properly with photos and details
|
||||
✓ Site is responsive and works on mobile devices
|
||||
✓ Search/filtering helps visitors find properties
|
||||
✓ MLS integration (if applicable) functions as designed
|
||||
✓ Email migration (if applicable) completed smoothly
|
||||
✓ Client is trained and confident using the system
|
||||
✓ Site is secure, fast, and professionally presented
|
||||
✓ All deliverables completed as specified in contract
|
||||
✓ Client is satisfied and relationship continues with hosting
|
||||
|
||||
|
||||
RISK MITIGATION
|
||||
================
|
||||
|
||||
Risks and mitigations built into contract:
|
||||
|
||||
Risk: Scope creep
|
||||
Mitigation: Clear deliverables list, exclusions, written change order process
|
||||
|
||||
Risk: Timeline delays from client
|
||||
Mitigation: Client responsibilities section, 30-day delay clause
|
||||
|
||||
Risk: MLS integration complexity
|
||||
Mitigation: Scoped as "planning" only, full IDX explicitly excluded
|
||||
|
||||
Risk: Design expectations exceed assets provided
|
||||
Mitigation: Design work limited to "consultation" and "customization"
|
||||
|
||||
Risk: Email migration more complex than expected
|
||||
Mitigation: Capped at 2 hours, additional time billed separately
|
||||
|
||||
Risk: Ongoing hosting costs unsustainable for startup
|
||||
Mitigation: Clear first-year total, ongoing cost transparency, 30-day cancel
|
||||
|
||||
Risk: Client wants features after launch
|
||||
Mitigation: 60-day warranty for bugs only, new features quoted separately
|
||||
|
||||
Risk: Non-payment
|
||||
Mitigation: $2,000 upfront, $4,600 due at launch before going live
|
||||
|
||||
|
||||
ALTERNATIVES IF NEEDED
|
||||
=======================
|
||||
|
||||
If budget is tight:
|
||||
OPTION A: Phased Approach
|
||||
- Phase 1: $4,000 - Basic site, manual property entry
|
||||
- Phase 2: $2,000 - ACF system and advanced features
|
||||
- Hosting: $600/year starting with Phase 1
|
||||
|
||||
OPTION B: Template-Based Site
|
||||
- $3,500 - Premium theme + basic customization
|
||||
- Hosting: $600/year
|
||||
- Faster launch, less custom
|
||||
|
||||
OPTION C: Monthly Payment Plan
|
||||
- $500/month x 12 months = $6,000 development
|
||||
- $50/month hosting
|
||||
- Total: $550/month first year
|
||||
|
||||
If timeline is urgent:
|
||||
OPTION D: Rush Fee
|
||||
- +$1,200 (20% premium) for immediate start
|
||||
- Total development: $7,200
|
||||
- Launch within 2 weeks
|
||||
|
||||
If scope is too much:
|
||||
OPTION E: Reduced Scope
|
||||
- $4,500 - Simpler site, fewer features
|
||||
- Manual property entry only (no ACF)
|
||||
- Basic theme customization
|
||||
- Hosting: $600/year
|
||||
|
||||
|
||||
NEXT STEP
|
||||
=========
|
||||
|
||||
Conduct client interview using: INTERVIEW-QUESTIONS-FOR-CLIENT.txt
|
||||
|
||||
This will answer all critical questions and allow final contract customization.
|
||||
@@ -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)
|
||||
+414
@@ -0,0 +1,414 @@
|
||||
WordPress Website Development Agreement
|
||||
HomeProz.com
|
||||
|
||||
Prepared by Hanson.xyz for HomeProz
|
||||
Date: [INSERT DATE]
|
||||
|
||||
|
||||
PROJECT OVERVIEW
|
||||
================
|
||||
|
||||
Hanson.xyz will design and develop a custom WordPress website for HomeProz. The website will provide an online presence for HomeProz's real estate services, featuring a custom property listing system that allows HomeProz staff to easily add and manage property listings through a backend interface. The site will be built using WordPress with Advanced Custom Fields (ACF) for property data entry, and will be styled using a theme modeled after the existing HomeProz design aesthetic.
|
||||
|
||||
The website will support both MLS-integrated listings (via Northstar MLS) and custom property listings for properties not on MLS (such as commercial real estate), providing flexibility for HomeProz's diverse inventory needs.
|
||||
|
||||
This project is estimated to require approximately 40 hours of development time and will be completed over approximately 1 week of active development time. Due to current project commitments, development will begin approximately 3-4 weeks from contract signing, with the site launching approximately 4-5 weeks from contract acceptance.
|
||||
|
||||
|
||||
PROJECT DELIVERABLES
|
||||
====================
|
||||
|
||||
The following deliverables will be provided as part of this project:
|
||||
|
||||
Design and Planning
|
||||
-------------------
|
||||
- Design consultation based on existing HomeProz branding and aesthetic
|
||||
- Property listing page layout and structure
|
||||
- Advanced Custom Fields (ACF) structure planning for property data
|
||||
|
||||
WordPress Development
|
||||
---------------------
|
||||
- Custom WordPress theme development based on existing HomeProz design
|
||||
- Responsive design implementation (mobile, tablet, desktop compatibility)
|
||||
- Homepage featuring property showcase and company information
|
||||
- Content pages with content block editor allowing for quick and clean creation of content pages
|
||||
- Property listing pages with custom fields for:
|
||||
- Property details (address, price, square footage, bedrooms, bathrooms, etc.)
|
||||
- Property descriptions
|
||||
- Photo galleries
|
||||
- MLS number field (for MLS-linked properties)
|
||||
- Property type categorization (residential, commercial, land, etc.)
|
||||
- Property status (active, pending, sold)
|
||||
- Property search and filtering functionality
|
||||
- Individual property detail pages with full information display
|
||||
- About/Company information page
|
||||
- Contact page with contact form and email notification
|
||||
- Browser compatibility testing (Chrome, Firefox, Safari, Edge)
|
||||
- Search engine optimization (SEO) basics (meta tags, semantic HTML, property schema markup)
|
||||
|
||||
Advanced Custom Fields (ACF) Implementation
|
||||
--------------------------------------------
|
||||
- Installation and configuration of Advanced Custom Fields Pro plugin
|
||||
- ACF Pro license ($49/year) included in development cost and managed by Developer (annual renewal billed as part of ongoing hosting/support)
|
||||
- Custom field groups for property listings including:
|
||||
- Basic property information fields
|
||||
- Pricing and financial details
|
||||
- Property features and amenities
|
||||
- Location and mapping data
|
||||
- Media upload fields for property photos
|
||||
- MLS integration field
|
||||
- Backend interface for easy property entry and management
|
||||
- Field validation and required field configuration
|
||||
|
||||
MLS Integration - Manual Entry
|
||||
-------------------------------
|
||||
- MLS number field in property listing system for manual entry
|
||||
- Documentation on MLS number entry workflow
|
||||
- Display of MLS number on property listings
|
||||
- NOTE: This is manual entry only; full automated IDX integration with property import/sync is NOT included and would be a separate future project if desired
|
||||
- NOTE: MLS account setup and any other third party services are the client's responsibility and billed separately by the providers themselves
|
||||
|
||||
Email Migration Support
|
||||
-----------------------
|
||||
- IT support consultation for migrating existing email to Gmail/Google Workspace
|
||||
- Guidance on Google Workspace setup and configuration
|
||||
- Email migration assistance (up to 2 hours of support included)
|
||||
- Documentation for ongoing email management
|
||||
|
||||
Content and Media
|
||||
-----------------
|
||||
- Integration of existing HomeProz branding, logos, and imagery
|
||||
- Migration of content from existing GoDaddy splash page
|
||||
- Integration of client-provided property photos and descriptions
|
||||
- Basic image editing and optimization for web use
|
||||
|
||||
Training and Documentation
|
||||
--------------------------
|
||||
- Training session (1-2 hours) for:
|
||||
- Adding and editing property listings via ACF backend
|
||||
- Managing property photos and galleries
|
||||
- Updating company information and pages
|
||||
- Basic WordPress content management
|
||||
- Written documentation for:
|
||||
- Property listing workflow
|
||||
- ACF field definitions and usage
|
||||
- WordPress admin basics
|
||||
- MLS integration process (if implemented)
|
||||
|
||||
Managed WordPress Hosting Setup
|
||||
--------------------------------
|
||||
- WordPress installation on Hanson.xyz managed hosting infrastructure
|
||||
- Domain migration from GoDaddy (or DNS pointing configuration)
|
||||
- SSL certificate installation and HTTPS configuration
|
||||
- Automated backup configuration (daily backups retained for 30 days)
|
||||
- Security hardening (firewall, security plugins, malware scanning)
|
||||
- Performance optimization (caching, CDN configuration)
|
||||
- Staging environment setup for testing updates
|
||||
- NOTE: Ongoing managed hosting is a separate service agreement detailed below
|
||||
|
||||
Testing and Launch
|
||||
------------------
|
||||
- Quality assurance testing across devices and browsers
|
||||
- Client review and feedback period
|
||||
- Bug fixes and adjustments based on client feedback
|
||||
- Deployment to production/live environment
|
||||
- Post-launch verification and testing
|
||||
|
||||
|
||||
EXCLUSIONS FROM SCOPE
|
||||
======================
|
||||
|
||||
This project specifically excludes the following, which can be quoted separately if desired:
|
||||
|
||||
- Full MLS IDX integration with automated property import (initial planning and MLS number field implementation is included; full IDX integration would require additional development and third-party service fees)
|
||||
- Custom plugin development beyond configuration of standard WordPress plugins
|
||||
- Logo design, branding, or graphic design services beyond web implementation
|
||||
- Ongoing website maintenance (covered under separate Managed Hosting Agreement)
|
||||
- Google Workspace account creation and billing (client responsibility)
|
||||
- Domain registration renewal fees (billed by GoDaddy or registrar)
|
||||
|
||||
|
||||
CLIENT RESPONSIBILITIES
|
||||
========================
|
||||
|
||||
To ensure timely completion of this project, the Client agrees to provide:
|
||||
|
||||
- All content for the website including:
|
||||
- Company description and "About" content
|
||||
- Service descriptions
|
||||
- Team member bios and photos (if applicable)
|
||||
- Contact information
|
||||
- Any existing property listings and photos
|
||||
- HomeProz logo files and branding assets in digital format
|
||||
- Access to GoDaddy account for domain DNS configuration
|
||||
- Access to existing email accounts for migration planning
|
||||
- Sample property data for testing the listing system during development
|
||||
|
||||
TIMELINE AND MILESTONES
|
||||
========================
|
||||
|
||||
The project will follow this general timeline:
|
||||
|
||||
Weeks 1-3: Pre-Development Queue Period
|
||||
- Contract execution and initial payment processing
|
||||
- Completion of current commitments (Auction Cast, Kodex, Ascent websites)
|
||||
- Client provides content, branding assets, and access credentials
|
||||
- Preliminary MLS and hosting planning
|
||||
|
||||
Week 4-5: Active Development (approximately 1 week of focused work)
|
||||
- Day 1-2: Kickoff meeting, requirements confirmation, ACF structure planning
|
||||
- Day 3-5: WordPress theme development and customization
|
||||
- Day 6-7: ACF implementation and property listing system build
|
||||
- Day 7-8: Content integration and page development
|
||||
- Day 8-9: Testing, client review on staging site, revisions
|
||||
- Day 10: Email migration support (if scheduled)
|
||||
|
||||
Week 5: Testing, Training, and Launch
|
||||
- Client feedback and revisions
|
||||
- Quality assurance testing
|
||||
- Training session on property listing management
|
||||
- Final client approval
|
||||
- Launch to production environment
|
||||
- Post-launch verification and email migration completion (if applicable)
|
||||
|
||||
Key milestone dates (to be confirmed upon contract signing):
|
||||
- Development start: Approximately 2-3 weeks after signing
|
||||
- Client review on staging: 1 week after development start
|
||||
- Final delivery: Approximately 6-7 weeks after contract signing
|
||||
- Training session: During week of launch
|
||||
|
||||
The Developer will make every reasonable effort to meet these timeline targets. The 2-3 week pre-development period is necessary due to existing project commitments and cannot be accelerated. In the event of unforeseen delays beyond this timeline, the Developer will communicate promptly with the Client. Extended delays caused by circumstances beyond the Developer's control (client feedback delays, third-party service issues, content provision delays, etc.) may result in adjusted timelines by mutual agreement.
|
||||
|
||||
|
||||
BUDGET AND PAYMENT TERMS
|
||||
=========================
|
||||
|
||||
WEBSITE DEVELOPMENT (ONE-TIME FEE)
|
||||
----------------------------------
|
||||
|
||||
This project is quoted as a fixed-fee engagement:
|
||||
|
||||
Total Website Development Cost: $6,000 (fixed fee)
|
||||
(Based on approximately 40 hours of development at $150/hour effective rate, discounted for startup client)
|
||||
|
||||
Payment Schedule:
|
||||
- $2,000 due upon contract signing to reserve development timeline
|
||||
- $4,000 due upon project completion, final delivery, and launch
|
||||
|
||||
Payment Methods:
|
||||
Payments may be made via check, ACH transfer, or credit card. Payment details and invoicing information will be provided upon contract execution.
|
||||
|
||||
The fixed-fee nature of this project means that the actual hours worked will not affect the final cost, provided the scope remains as defined in this agreement. The 40-hour estimate is provided for planning purposes. This price is firm and non-negotiable.
|
||||
|
||||
|
||||
MANAGED HOSTING SERVICE (ONGOING ANNUAL FEE)
|
||||
---------------------------------------------
|
||||
|
||||
In addition to the one-time website development cost, HomeProz will subscribe to Hanson.xyz's Managed WordPress Hosting service:
|
||||
|
||||
Annual Managed Hosting Fee: $600 per year (billed annually)
|
||||
(Equivalent to $50/month, but billed once per year for administrative simplicity)
|
||||
|
||||
Managed hosting includes:
|
||||
- WordPress hosting on high-performance servers
|
||||
- Daily automated backups retained for 30 days
|
||||
- Security monitoring and malware scanning
|
||||
- WordPress core, theme, and plugin updates (including ACF Pro license renewal)
|
||||
- SSL certificate management and renewal
|
||||
- Server maintenance and performance optimization
|
||||
- Staging environment for testing updates
|
||||
- Technical support for hosting-related issues (up to 2 hours/month)
|
||||
- ACF Pro plugin license maintenance and annual renewal
|
||||
- 99.9% uptime guarantee
|
||||
|
||||
Hosting Payment Terms:
|
||||
- First year hosting fee due upon website launch: $600
|
||||
- Subsequent annual renewals due on anniversary of launch date
|
||||
- Invoiced 30 days prior to renewal date
|
||||
- Payment terms: Net 15 days from invoice date
|
||||
- Billing is annual only; monthly billing is not available for this service
|
||||
|
||||
Hosting Service Agreement:
|
||||
- Minimum commitment: 1 year from launch date
|
||||
- Auto-renewal annually unless 30 days notice provided
|
||||
- Service may be terminated by either party with 30 days written notice
|
||||
- Upon termination, client may request site backup and migration assistance (billed at hourly rate of $175/hour)
|
||||
|
||||
NOTES ON HOSTING COSTS:
|
||||
- This represents significant savings compared to comparable managed WordPress hosting services (typically $75-150/month for similar service levels)
|
||||
- The $50/month rate ($20 hosting + $30 management) provides peace of mind that a real person is monitoring and maintaining the site
|
||||
|
||||
|
||||
ADDITIONAL SERVICES (BILLED SEPARATELY)
|
||||
----------------------------------------
|
||||
|
||||
The following services are client responsibilities and billed separately:
|
||||
|
||||
Northstar MLS (if client chooses to subscribe):
|
||||
- Application fee: $100 (one-time, paid to Northstar MLS)
|
||||
- Monthly subscription: $55/month (paid to Northstar MLS)
|
||||
- Hanson.xyz is not involved in MLS billing
|
||||
|
||||
Google Workspace for Email (if client chooses Gmail migration):
|
||||
- Approximate cost: $6-12 per user per month (paid to Google)
|
||||
- Hanson.xyz is not involved in Google Workspace billing
|
||||
- Email migration assistance (up to 2 hours) is included in development cost
|
||||
|
||||
Domain Registration Renewal:
|
||||
- Annual renewal through current registrar (GoDaddy or transferred registrar)
|
||||
- Approximate cost: $15-20/year (paid to registrar)
|
||||
- Hanson.xyz can manage domain renewal if client prefers (billed at cost + $25/year management fee)
|
||||
|
||||
|
||||
TOTAL FIRST YEAR INVESTMENT SUMMARY
|
||||
------------------------------------
|
||||
|
||||
Website Development (one-time): $6,000
|
||||
Managed Hosting (first year): $600
|
||||
TOTAL FIRST YEAR: $6,600
|
||||
|
||||
Optional add-ons (if chosen):
|
||||
+ Northstar MLS: $100 setup + $660/year ($55/month)
|
||||
+ Google Workspace: ~$72-144/year per user ($6-12/month)
|
||||
|
||||
Year 2 and beyond (annual recurring):
|
||||
Managed Hosting: $600/year
|
||||
+ Optional MLS: $660/year
|
||||
+ Optional Google Workspace: ~$72-144/year per user
|
||||
|
||||
|
||||
CHANGE REQUESTS
|
||||
===============
|
||||
|
||||
After the scope of work has been agreed upon and this contract is signed, any changes requested by the Client to the scope of work must be approved in writing by both parties before they can be implemented.
|
||||
|
||||
If the Developer determines that the requested changes are feasible and agrees to perform the additional work, the Developer will provide a quote at the rate of $250 per hour for the additional work. 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.
|
||||
|
||||
Due to the fixed-fee nature of this project, scope management is critical to staying on timeline and budget. The Developer encourages the Client to carefully review the deliverables section and raise any questions before signing this agreement.
|
||||
|
||||
|
||||
CONTRACT LEGAL TERMS
|
||||
====================
|
||||
|
||||
Project Description
|
||||
-------------------
|
||||
This agreement (the "Agreement") is made between Hanson.xyz (the "Developer"), and HomeProz (the "Client").
|
||||
|
||||
The Developer and the Client hereby agree to the terms set forth in this document for the design and development of a WordPress website as described in the Project Deliverables section above.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
Intellectual Property and Work Product
|
||||
---------------------------------------
|
||||
Client Content: All content, data, and materials provided by Client remain Client's property. Client grants Developer a license to use such materials solely for performing the Services.
|
||||
|
||||
Work Product Ownership: Upon full payment, Client owns the completed website, including the design, content organization, and custom configurations specific to Client's business. Developer assigns all rights in this client-specific Work Product to Client.
|
||||
|
||||
Developer Retained Rights: Developer retains ownership of all general-purpose code, techniques, tools, libraries, methods, and frameworks (whether pre-existing or developed during this project) that have utility beyond Client's specific business needs. Developer may reuse such materials in future projects. Client receives a perpetual, royalty-free license to use these materials as integrated into Client's website.
|
||||
|
||||
This includes WordPress core software (GPL licensed), third-party themes/plugins (subject to their respective licenses), and general development tools.
|
||||
|
||||
|
||||
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 'Project Deliverables' section at no additional cost.
|
||||
|
||||
This warranty covers:
|
||||
- Bugs or errors in custom code developed by the Developer
|
||||
- Functionality that does not work as designed and agreed upon
|
||||
- Critical issues preventing the website from functioning properly
|
||||
|
||||
This warranty does not cover:
|
||||
- Problems with third-party plugins, themes, or services not developed by the Developer
|
||||
- Hosting, server, or infrastructure issues beyond the Developer's control
|
||||
- New feature requests or enhancements beyond the original scope
|
||||
|
||||
After the expiration of the warranty period, any additional changes, modifications, or support for the functionality provided will be quoted separately from this agreement.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
The Client acknowledges that websites depend on third-party services and technologies (hosting providers, domain registrars, WordPress core software, plugins, browsers, etc.) that are outside the Developer's control. The Developer is not liable for failures, outages, or issues caused by these third-party dependencies.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
The Client represents and warrants that all content, images, text, trademarks, and materials provided to the Developer for use in the website are either owned by the Client or the Client has obtained all necessary permissions, licenses, and rights to use such materials. The Client agrees to indemnify and hold the Developer harmless from any claims of copyright infringement, trademark infringement, or other intellectual property violations related to Client-provided content.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
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. This may include screenshots, descriptions, and links to the live website in the Developer's portfolio, marketing materials, and case studies.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
Any verbal agreements, promises, or understandings not documented in this written agreement are not binding and shall not be enforceable.
|
||||
|
||||
|
||||
Severability
|
||||
------------
|
||||
If any provision of this agreement is found to be invalid or unenforceable, the remaining provisions shall continue in full force and effect.
|
||||
|
||||
|
||||
Delivery Timeline
|
||||
-----------------
|
||||
The developer will make every reasonable effort to deliver the project within the timeline specified in the Timeline and Milestones section. 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 due to Developer delays (not including delays caused by Client feedback, content provision, or third-party service issues), the client reserves the right to terminate this agreement at their discretion. In the event of such termination, any payments made will be reconciled based on work completed to date at the rate of $175/hour, with any excess refunded to the Client.
|
||||
|
||||
|
||||
Termination
|
||||
-----------
|
||||
Either party may terminate this agreement with written notice if:
|
||||
- The other party materially breaches the agreement and fails to cure within 15 days of written notice
|
||||
- The project is delayed more than 60 days beyond the estimated completion date due to circumstances within the terminating party's control
|
||||
|
||||
Upon termination:
|
||||
- Client will pay for all work completed to date at the rate of $175/hour
|
||||
- Developer will deliver all work completed to date
|
||||
- Both parties will return or destroy confidential information of the other party
|
||||
- Any payments made in excess of work completed will be refunded to Client
|
||||
|
||||
|
||||
ACCEPTANCE AND SIGNATURES
|
||||
==========================
|
||||
|
||||
By signing below, both parties acknowledge that they have read, understood, and agree to all terms and conditions set forth in this Agreement.
|
||||
|
||||
|
||||
FOR HOMEPROZ:
|
||||
|
||||
Signature: _________________________________ Date: _______________
|
||||
|
||||
Printed Name: _________________________________
|
||||
|
||||
Title: _________________________________
|
||||
|
||||
|
||||
FOR HANSON.XYZ:
|
||||
|
||||
Signature: _________________________________ Date: _______________
|
||||
|
||||
Printed Name: Brian Hanson
|
||||
|
||||
Title: Owner
|
||||
+562
@@ -0,0 +1,562 @@
|
||||
WordPress Website Development Agreement
|
||||
HomeProz.com
|
||||
|
||||
Prepared by Hanson.xyz for HomeProz
|
||||
Date: [INSERT DATE]
|
||||
|
||||
|
||||
PROJECT OVERVIEW
|
||||
================
|
||||
|
||||
Hanson.xyz will design and develop a custom WordPress website for HomeProz. The website will provide an online presence
|
||||
for HomeProz's real estate services, featuring a custom property listing
|
||||
system that allows HomeProz staff to easily add and manage property listings
|
||||
through a backend interface. The site will be built using WordPress with
|
||||
Advanced Custom Fields (ACF) for property data entry, and will be styled
|
||||
using a theme modeled after the existing HomeProz design aesthetic.
|
||||
|
||||
The website will support both MLS-integrated listings (via Northstar MLS) and
|
||||
custom property listings for properties not on MLS (such as commercial real
|
||||
estate), providing flexibility for HomeProz's diverse inventory needs.
|
||||
|
||||
This project is estimated to require approximately 40 hours of development
|
||||
time and will be completed over approximately 1 week of active development
|
||||
time. Due to current project commitments, development will begin approximately
|
||||
3-4 weeks from contract signing, with the site launching approximately 4-5
|
||||
weeks from contract acceptance.
|
||||
|
||||
|
||||
PROJECT DELIVERABLES
|
||||
====================
|
||||
|
||||
The following deliverables will be provided as part of this project:
|
||||
|
||||
Design and Planning
|
||||
-------------------
|
||||
- Design consultation based on existing HomeProz branding and aesthetic
|
||||
- Theme selection and customization planning
|
||||
- Property listing page layout and structure
|
||||
- User flow planning for property search and browsing
|
||||
- Advanced Custom Fields (ACF) structure planning for property data
|
||||
|
||||
WordPress Development
|
||||
---------------------
|
||||
- Custom WordPress theme development or child theme based on existing HomeProz design
|
||||
- Responsive design implementation (mobile, tablet, desktop compatibility)
|
||||
- Homepage featuring property showcase and company information
|
||||
- Property listing pages with custom fields for:
|
||||
- Property details (address, price, square footage, bedrooms, bathrooms, etc.)
|
||||
- Property descriptions
|
||||
- Photo galleries
|
||||
- MLS number field (for MLS-linked properties)
|
||||
- Property type categorization (residential, commercial, land, etc.)
|
||||
- Property status (active, pending, sold)
|
||||
- Property search and filtering functionality
|
||||
- Individual property detail pages with full information display
|
||||
- About/Company information page
|
||||
- Contact page with contact form and email notification
|
||||
- Browser compatibility testing (Chrome, Firefox, Safari, Edge)
|
||||
- Performance optimization (image compression, caching configuration)
|
||||
- Search engine optimization (SEO) basics (meta tags, semantic HTML, property schema markup)
|
||||
|
||||
Advanced Custom Fields (ACF) Implementation
|
||||
--------------------------------------------
|
||||
- Installation and configuration of Advanced Custom Fields Pro plugin
|
||||
- ACF Pro license ($49/year) included in development cost and managed by Developer
|
||||
(annual renewal billed as part of ongoing hosting/support)
|
||||
- Custom field groups for property listings including:
|
||||
- Basic property information fields
|
||||
- Pricing and financial details
|
||||
- Property features and amenities
|
||||
- Location and mapping data
|
||||
- Media upload fields for property photos
|
||||
- MLS integration field
|
||||
- Backend interface for easy property entry and management
|
||||
- Field validation and required field configuration
|
||||
|
||||
MLS Integration - Manual Entry
|
||||
-------------------------------
|
||||
- MLS number field in property listing system for manual entry
|
||||
- Documentation on MLS number entry workflow
|
||||
- Display of MLS number on property listings
|
||||
- NOTE: This is manual entry only; full automated IDX integration with property
|
||||
import/sync is NOT included and would be a separate future project if desired
|
||||
- NOTE: MLS account setup ($100 application + $55/month subscription) is
|
||||
the client's responsibility and billed separately by Northstar MLS
|
||||
|
||||
Email Migration Support
|
||||
-----------------------
|
||||
- IT support consultation for migrating existing email to Gmail/Google Workspace
|
||||
- Guidance on Google Workspace setup and configuration
|
||||
- Email migration assistance (up to 2 hours of support included)
|
||||
- Documentation for ongoing email management
|
||||
|
||||
Content and Media
|
||||
-----------------
|
||||
- Integration of existing HomeProz branding, logos, and imagery
|
||||
- Migration of content from existing GoDaddy splash page
|
||||
- Integration of client-provided property photos and descriptions
|
||||
- Basic image editing and optimization for web use
|
||||
|
||||
Training and Documentation
|
||||
--------------------------
|
||||
- Training session (1-2 hours) for:
|
||||
- Adding and editing property listings via ACF backend
|
||||
- Managing property photos and galleries
|
||||
- Updating company information and pages
|
||||
- Basic WordPress content management
|
||||
- Written documentation for:
|
||||
- Property listing workflow
|
||||
- ACF field definitions and usage
|
||||
- WordPress admin basics
|
||||
- MLS integration process (if implemented)
|
||||
|
||||
Managed WordPress Hosting Setup
|
||||
--------------------------------
|
||||
- WordPress installation on Hanson.xyz managed hosting infrastructure
|
||||
- Domain migration from GoDaddy (or DNS pointing configuration)
|
||||
- SSL certificate installation and HTTPS configuration
|
||||
- Automated backup configuration (daily backups retained for 30 days)
|
||||
- Security hardening (firewall, security plugins, malware scanning)
|
||||
- Performance optimization (caching, CDN configuration)
|
||||
- Staging environment setup for testing updates
|
||||
- NOTE: Ongoing managed hosting is a separate service agreement detailed below
|
||||
|
||||
Testing and Launch
|
||||
------------------
|
||||
- Quality assurance testing across devices and browsers
|
||||
- Client review and feedback period
|
||||
- Bug fixes and adjustments based on client feedback
|
||||
- Deployment to production/live environment
|
||||
- Post-launch verification and testing
|
||||
|
||||
|
||||
EXCLUSIONS FROM SCOPE
|
||||
======================
|
||||
|
||||
This project specifically excludes the following, which can be quoted
|
||||
separately if desired:
|
||||
|
||||
- Full MLS IDX integration with automated property import (initial planning
|
||||
and MLS number field implementation is included; full IDX integration would
|
||||
require additional development and third-party service fees)
|
||||
- E-commerce functionality or online payment processing
|
||||
- Custom plugin development beyond configuration of standard WordPress plugins
|
||||
- Content writing, copywriting, or professional photography services
|
||||
- Logo design, branding, or graphic design services beyond web implementation
|
||||
- Ongoing website maintenance (covered under separate Managed Hosting Agreement)
|
||||
- Google Workspace account creation and billing (client responsibility)
|
||||
- Email content migration assistance beyond the 2 hours included
|
||||
- Integration with third-party CRM systems (e.g., Salesforce, HubSpot)
|
||||
- Custom mortgage calculators or financial tools
|
||||
- Lead generation or marketing automation tools
|
||||
- Virtual tour or 3D property viewing integrations
|
||||
- Mobile application development
|
||||
- Ongoing MLS subscription fees ($55/month billed by Northstar MLS)
|
||||
- Ongoing Google Workspace fees (if applicable)
|
||||
- Domain registration renewal fees (billed by GoDaddy or registrar)
|
||||
|
||||
|
||||
CLIENT RESPONSIBILITIES
|
||||
========================
|
||||
|
||||
To ensure timely completion of this project, the Client agrees to provide:
|
||||
|
||||
- All content for the website including:
|
||||
- Company description and "About" content
|
||||
- Service descriptions
|
||||
- Team member bios and photos (if applicable)
|
||||
- Contact information
|
||||
- Any existing property listings and photos
|
||||
- HomeProz logo files and branding assets in digital format
|
||||
- Timely feedback on design and development milestones (within 5 business days)
|
||||
- Access to GoDaddy account for domain DNS configuration
|
||||
- Access to existing email accounts for migration planning
|
||||
- Decision-making authority or timely internal approvals for design and features
|
||||
- Registration and payment for Northstar MLS account (if MLS integration desired)
|
||||
- Registration and payment for Google Workspace (if Gmail migration desired)
|
||||
- Sample property data for testing the listing system during development
|
||||
|
||||
Delays in providing the above items may impact the project timeline. The
|
||||
Developer will make reasonable efforts to accommodate delays, but extended
|
||||
delays beyond 30 days may result in timeline adjustments or project suspension
|
||||
until client materials are provided.
|
||||
|
||||
|
||||
TIMELINE AND MILESTONES
|
||||
========================
|
||||
|
||||
The project will follow this general timeline:
|
||||
|
||||
Weeks 1-3: Pre-Development Queue Period
|
||||
- Contract execution and initial payment processing
|
||||
- Completion of current commitments (Auction Cast, Kodex, Ascent websites)
|
||||
- Client provides content, branding assets, and access credentials
|
||||
- Preliminary MLS and hosting planning
|
||||
|
||||
Week 4-5: Active Development (approximately 1 week of focused work)
|
||||
- Day 1-2: Kickoff meeting, requirements confirmation, ACF structure planning
|
||||
- Day 3-5: WordPress theme development and customization
|
||||
- Day 6-7: ACF implementation and property listing system build
|
||||
- Day 7-8: Content integration and page development
|
||||
- Day 8-9: Testing, client review on staging site, revisions
|
||||
- Day 10: Email migration support (if scheduled)
|
||||
|
||||
Week 5: Testing, Training, and Launch
|
||||
- Client feedback and revisions
|
||||
- Quality assurance testing
|
||||
- Training session on property listing management
|
||||
- Final client approval
|
||||
- Launch to production environment
|
||||
- Post-launch verification and email migration completion (if applicable)
|
||||
|
||||
Key milestone dates (to be confirmed upon contract signing):
|
||||
- Contract signing: [INSERT DATE]
|
||||
- Development start: Approximately 3-4 weeks after signing
|
||||
- Client review on staging: 1 week after development start
|
||||
- Final delivery: Approximately 4-5 weeks after contract signing
|
||||
- Training session: During week of launch
|
||||
|
||||
The Developer will make every reasonable effort to meet these timeline
|
||||
targets. The 3-4 week pre-development period is necessary due to existing
|
||||
project commitments (Auction Cast, Kodex, and Ascent websites) and cannot
|
||||
be accelerated. In the event of unforeseen delays beyond this timeline, the
|
||||
Developer will communicate promptly with the Client. Extended delays caused
|
||||
by circumstances beyond the Developer's control (client feedback delays,
|
||||
third-party service issues, content provision delays, etc.) may result in
|
||||
adjusted timelines by mutual agreement.
|
||||
|
||||
|
||||
BUDGET AND PAYMENT TERMS
|
||||
=========================
|
||||
|
||||
WEBSITE DEVELOPMENT (ONE-TIME FEE)
|
||||
----------------------------------
|
||||
|
||||
This project is quoted as a fixed-fee engagement:
|
||||
|
||||
Total Website Development Cost: $6,000 (fixed fee)
|
||||
(Based on approximately 40 hours of development at $150/hour effective rate,
|
||||
discounted for startup client)
|
||||
|
||||
Payment Schedule:
|
||||
- $2,000 due upon contract signing to reserve development timeline
|
||||
- $4,000 due upon project completion, final delivery, and launch
|
||||
|
||||
Payment Methods:
|
||||
Payments may be made via check, ACH transfer, or credit card. Payment details
|
||||
and invoicing information will be provided upon contract execution.
|
||||
|
||||
The fixed-fee nature of this project means that the actual hours worked will
|
||||
not affect the final cost, provided the scope remains as defined in this
|
||||
agreement. The 40-hour estimate is provided for planning purposes. This price
|
||||
is firm and non-negotiable.
|
||||
|
||||
|
||||
MANAGED HOSTING SERVICE (ONGOING ANNUAL FEE)
|
||||
---------------------------------------------
|
||||
|
||||
In addition to the one-time website development cost, HomeProz will subscribe
|
||||
to Hanson.xyz's Managed WordPress Hosting service:
|
||||
|
||||
Annual Managed Hosting Fee: $600 per year (billed annually)
|
||||
(Equivalent to $50/month, but billed once per year for administrative simplicity)
|
||||
|
||||
Managed hosting includes:
|
||||
- WordPress hosting on high-performance servers
|
||||
- Daily automated backups retained for 30 days
|
||||
- Security monitoring and malware scanning
|
||||
- WordPress core, theme, and plugin updates (including ACF Pro license renewal)
|
||||
- SSL certificate management and renewal
|
||||
- Server maintenance and performance optimization
|
||||
- Staging environment for testing updates
|
||||
- Technical support for hosting-related issues (up to 2 hours/month)
|
||||
- ACF Pro plugin license maintenance and annual renewal
|
||||
- 99.9% uptime guarantee
|
||||
|
||||
Hosting Payment Terms:
|
||||
- First year hosting fee due upon website launch: $600
|
||||
- Subsequent annual renewals due on anniversary of launch date
|
||||
- Invoiced 30 days prior to renewal date
|
||||
- Payment terms: Net 15 days from invoice date
|
||||
- Billing is annual only; monthly billing is not available for this service
|
||||
|
||||
Hosting Service Agreement:
|
||||
- Minimum commitment: 1 year from launch date
|
||||
- Auto-renewal annually unless 30 days notice provided
|
||||
- Service may be terminated by either party with 30 days written notice
|
||||
- Upon termination, client may request site backup and migration assistance
|
||||
(billed at hourly rate of $175/hour)
|
||||
|
||||
NOTES ON HOSTING COSTS:
|
||||
- This represents significant savings compared to comparable managed WordPress
|
||||
hosting services (typically $75-150/month for similar service levels)
|
||||
- Includes human support rather than automated ticketing systems
|
||||
- The $50/month rate ($20 hosting + $30 management) provides peace of mind
|
||||
that a real person is monitoring and maintaining the site
|
||||
|
||||
|
||||
ADDITIONAL SERVICES (BILLED SEPARATELY)
|
||||
----------------------------------------
|
||||
|
||||
The following services are client responsibilities and billed separately:
|
||||
|
||||
Northstar MLS (if client chooses to subscribe):
|
||||
- Application fee: $100 (one-time, paid to Northstar MLS)
|
||||
- Monthly subscription: $55/month (paid to Northstar MLS)
|
||||
- Hanson.xyz is not involved in MLS billing
|
||||
|
||||
Google Workspace for Email (if client chooses Gmail migration):
|
||||
- Approximate cost: $6-12 per user per month (paid to Google)
|
||||
- Hanson.xyz is not involved in Google Workspace billing
|
||||
- Email migration assistance (up to 2 hours) is included in development cost
|
||||
|
||||
Domain Registration Renewal:
|
||||
- Annual renewal through current registrar (GoDaddy or transferred registrar)
|
||||
- Approximate cost: $15-20/year (paid to registrar)
|
||||
- Hanson.xyz can manage domain renewal if client prefers (billed at cost + $25/year management fee)
|
||||
|
||||
|
||||
TOTAL FIRST YEAR INVESTMENT SUMMARY
|
||||
------------------------------------
|
||||
|
||||
Website Development (one-time): $6,000
|
||||
Managed Hosting (first year): $600
|
||||
TOTAL FIRST YEAR: $6,600
|
||||
|
||||
Optional add-ons (if chosen):
|
||||
+ Northstar MLS: $100 setup + $660/year ($55/month)
|
||||
+ Google Workspace: ~$72-144/year per user ($6-12/month)
|
||||
|
||||
Year 2 and beyond (annual recurring):
|
||||
Managed Hosting: $600/year
|
||||
+ Optional MLS: $660/year
|
||||
+ Optional Google Workspace: ~$72-144/year per user
|
||||
|
||||
|
||||
CHANGE REQUESTS
|
||||
===============
|
||||
|
||||
After the scope of work has been agreed upon and this contract is signed, any
|
||||
changes requested by the Client to the scope of work must be approved in
|
||||
writing by both parties before they can be implemented.
|
||||
|
||||
If the Developer determines that the requested changes are feasible and agrees
|
||||
to perform the additional work, the Developer will provide a quote at the rate
|
||||
of $250 per hour for the additional work. 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.
|
||||
|
||||
Due to the fixed-fee nature of this project, scope management is critical to
|
||||
staying on timeline and budget. The Developer encourages the Client to
|
||||
carefully review the deliverables section and raise any questions before
|
||||
signing this agreement.
|
||||
|
||||
|
||||
CONTRACT LEGAL TERMS
|
||||
====================
|
||||
|
||||
Project Description
|
||||
-------------------
|
||||
This agreement (the "Agreement") is made between Hanson.xyz (the "Developer"),
|
||||
and HomeProz (the "Client").
|
||||
|
||||
The Developer and the Client hereby agree to the terms set forth in this
|
||||
document for the design and development of a WordPress website as described
|
||||
in the Project Deliverables section above.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
Intellectual Property and Work Product
|
||||
---------------------------------------
|
||||
All right, title and interest, including copyright and other intellectual
|
||||
property rights in and to any data, information, ideas, concepts or material
|
||||
provided by Client to Developer for use in performing Services are and shall
|
||||
remain Client's property ("Client Content"). Client grants Developer a
|
||||
non-exclusive, non-transferable license during the term of this agreement to
|
||||
reproduce, display and perform Client Content solely in connection with, and
|
||||
solely as required for, the performance of the Services. Client Content shall
|
||||
be considered Confidential Information of Client.
|
||||
|
||||
As between the parties, Developer agrees that Client is the sole and exclusive
|
||||
owner of all inventions, improvements, computer programs, discoveries, ideas,
|
||||
processes, systems, writings or other works authored, developed, discovered,
|
||||
or conceived by Developer, solely or jointly with others, that are produced
|
||||
as part of, or in the course of performing, the Services (collectively, "Work
|
||||
Product"). Developer agrees to assign, and hereby assigns, to Client all
|
||||
rights, title and interest it may have in or to the Work Product, including
|
||||
without limitation all patent rights, trademark rights, copyrights, trade
|
||||
secret rights, and other intellectual property or proprietary rights therein.
|
||||
|
||||
Developer shall retain all ownership rights in and to any pre-existing
|
||||
materials, libraries, tools, utilities, frameworks, or code developed
|
||||
independently of the Services (collectively, "Developer Tools"), even if such
|
||||
Developer Tools are incorporated into the Work Product. To the extent any
|
||||
Developer Tools are included in the Work Product, Developer hereby grants
|
||||
Client a non-exclusive, royalty-free, non-sublicensable (except as necessary
|
||||
to use the Work Product), non-transferable (except to a successor in interest),
|
||||
worldwide, perpetual license to use such Developer Tools solely as part of the
|
||||
Work Product.
|
||||
|
||||
This includes but is not limited to: WordPress core software (GPL licensed),
|
||||
third-party WordPress themes or plugins (subject to their respective licenses),
|
||||
code libraries, frameworks, and development tools used in the creation of the
|
||||
website.
|
||||
|
||||
|
||||
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 'Project Deliverables'
|
||||
section at no additional cost.
|
||||
|
||||
This warranty covers:
|
||||
- Bugs or errors in custom code developed by the Developer
|
||||
- Functionality that does not work as designed and agreed upon
|
||||
- Critical issues preventing the website from functioning properly
|
||||
|
||||
This warranty does not cover:
|
||||
- Issues caused by changes made by the Client or third parties after delivery
|
||||
- Problems with third-party plugins, themes, or services not developed by
|
||||
the Developer
|
||||
- Hosting, server, or infrastructure issues beyond the Developer's control
|
||||
- New feature requests or enhancements beyond the original scope
|
||||
- Issues caused by Client's failure to maintain WordPress core, theme, or
|
||||
plugin updates
|
||||
|
||||
After the expiration of the warranty period, any additional changes,
|
||||
modifications, or support for the functionality provided will be quoted
|
||||
separately from this agreement.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
The Client acknowledges that websites depend on third-party services and
|
||||
technologies (hosting providers, domain registrars, WordPress core software,
|
||||
plugins, browsers, etc.) that are outside the Developer's control. The
|
||||
Developer is not liable for failures, outages, or issues caused by these
|
||||
third-party dependencies.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
The Client represents and warrants that all content, images, text, trademarks,
|
||||
and materials provided to the Developer for use in the website are either
|
||||
owned by the Client or the Client has obtained all necessary permissions,
|
||||
licenses, and rights to use such materials. The Client agrees to indemnify
|
||||
and hold the Developer harmless from any claims of copyright infringement,
|
||||
trademark infringement, or other intellectual property violations related to
|
||||
Client-provided content.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
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. This may include screenshots,
|
||||
descriptions, and links to the live website in the Developer's portfolio,
|
||||
marketing materials, and case studies.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
Any verbal agreements, promises, or understandings not documented in this
|
||||
written agreement are not binding and shall not be enforceable.
|
||||
|
||||
|
||||
Severability
|
||||
------------
|
||||
If any provision of this agreement is found to be invalid or unenforceable,
|
||||
the remaining provisions shall continue in full force and effect.
|
||||
|
||||
|
||||
Delivery Timeline
|
||||
-----------------
|
||||
The developer will make every reasonable effort to deliver the project within
|
||||
the timeline specified in the Timeline and Milestones section. 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 due to
|
||||
Developer delays (not including delays caused by Client feedback, content
|
||||
provision, or third-party service issues), the client reserves the right to
|
||||
terminate this agreement at their discretion. In the event of such termination,
|
||||
any payments made will be reconciled based on work completed to date at the
|
||||
rate of $175/hour, with any excess refunded to the Client.
|
||||
|
||||
|
||||
Termination
|
||||
-----------
|
||||
Either party may terminate this agreement with written notice if:
|
||||
- The other party materially breaches the agreement and fails to cure within
|
||||
15 days of written notice
|
||||
- The project is delayed more than 60 days beyond the estimated completion
|
||||
date due to circumstances within the terminating party's control
|
||||
|
||||
Upon termination:
|
||||
- Client will pay for all work completed to date at the rate of $175/hour
|
||||
- Developer will deliver all work completed to date
|
||||
- Both parties will return or destroy confidential information of the other
|
||||
party
|
||||
- Any payments made in excess of work completed will be refunded to Client
|
||||
|
||||
|
||||
ACCEPTANCE AND SIGNATURES
|
||||
==========================
|
||||
|
||||
By signing below, both parties acknowledge that they have read, understood,
|
||||
and agree to all terms and conditions set forth in this Agreement.
|
||||
|
||||
|
||||
FOR HOMEPROZ:
|
||||
|
||||
Signature: _________________________________ Date: _______________
|
||||
|
||||
Printed Name: _________________________________
|
||||
|
||||
Title: _________________________________
|
||||
|
||||
|
||||
FOR HANSON.XYZ:
|
||||
|
||||
Signature: _________________________________ Date: _______________
|
||||
|
||||
Printed Name: Brian Hanson
|
||||
|
||||
Title: Owner
|
||||
@@ -0,0 +1,542 @@
|
||||
HOMEPROZ WORDPRESS CONTRACT - FEEDBACK, QUESTIONS & RECOMMENDATIONS
|
||||
====================================================================
|
||||
Date: October 29, 2025
|
||||
|
||||
|
||||
OVERVIEW
|
||||
========
|
||||
|
||||
The draft contract has been completed and is ready for customization. The
|
||||
contract follows the structure and legal framework of your successful Landproz
|
||||
contracts, adapted for a WordPress website build project.
|
||||
|
||||
Files created:
|
||||
1. DRAFT-HomeProz-WordPress-Website-Contract.txt - Main contract (ready for customization)
|
||||
2. CONTRACT-KEY-ELEMENTS-EXTRACTED.txt - Reference guide of all elements used
|
||||
3. reference_examples/ directory - All source Landproz contracts in text format
|
||||
|
||||
|
||||
CRITICAL QUESTIONS - MUST ANSWER BEFORE FINALIZING
|
||||
===================================================
|
||||
|
||||
1. WHAT EXACTLY ARE YOU BUILDING?
|
||||
Location in contract: PROJECT OVERVIEW and PROJECT DELIVERABLES sections
|
||||
|
||||
Questions:
|
||||
- What type of website is this? (brochure site, property listings, services site?)
|
||||
- How many pages? (e.g., Home, About, Services, Contact, etc.)
|
||||
- What specific features are needed? (contact forms, maps, property search, etc.)
|
||||
- Are there any special integrations? (CRM, third-party services, etc.)
|
||||
- Is this a new site or redesign of existing site?
|
||||
- Do they have existing content or will you help create it?
|
||||
|
||||
Action needed:
|
||||
Fill in the [INSERT] placeholders in these sections with specific deliverables.
|
||||
|
||||
|
||||
2. WHAT IS THE TIMELINE?
|
||||
Location in contract: PROJECT OVERVIEW and TIMELINE AND MILESTONES sections
|
||||
|
||||
Questions:
|
||||
- When does the client want to launch?
|
||||
- How quickly can they provide content and feedback?
|
||||
- Are there any hard deadlines or event dates?
|
||||
- 40 hours over how many weeks? (2 weeks? 4 weeks? 6 weeks?)
|
||||
|
||||
Current draft assumes: 4 weeks with weekly milestones
|
||||
|
||||
Action needed:
|
||||
- Insert specific start date
|
||||
- Insert milestone dates (design approval, development review, launch)
|
||||
- Adjust timeline if needed based on project complexity
|
||||
|
||||
|
||||
3. WHAT IS THE PAYMENT STRUCTURE?
|
||||
Location in contract: BUDGET AND PAYMENT TERMS section
|
||||
|
||||
The contract currently shows three options:
|
||||
Option A: $2,500 upfront, $4,500 on completion
|
||||
Option B: Full $7,000 on delivery, net 30 terms
|
||||
Option C: Custom schedule
|
||||
|
||||
Questions:
|
||||
- Do you want money upfront to secure commitment? (recommended)
|
||||
- Does the client prefer net 30 terms or immediate payment?
|
||||
- Is there a deposit policy?
|
||||
|
||||
Recommendation:
|
||||
Option A (split payment) is recommended for new clients:
|
||||
- Upfront payment shows commitment
|
||||
- Reduces risk of non-payment
|
||||
- Aligns with your 2023 Landproz contract pattern ($12k upfront on $36k project)
|
||||
- Consider 30-50% upfront is standard
|
||||
|
||||
Action needed:
|
||||
Choose payment option and delete the others, or create custom schedule.
|
||||
|
||||
|
||||
4. HOSTING RESPONSIBILITY?
|
||||
Location in contract: PROJECT DELIVERABLES > Hosting and Technical Setup
|
||||
|
||||
Questions:
|
||||
- Will you set up hosting or will they provide it?
|
||||
- If you're setting it up, which hosting provider?
|
||||
- Is hosting cost included in the $7,000 or billed separately?
|
||||
- Are you providing ongoing hosting management or one-time setup?
|
||||
|
||||
Action needed:
|
||||
Clarify hosting responsibilities in the deliverables section.
|
||||
|
||||
|
||||
5. WHAT'S EXCLUDED?
|
||||
Location in contract: EXCLUSIONS FROM SCOPE section
|
||||
|
||||
The draft includes common exclusions, but you should review:
|
||||
- Are you doing logo/branding work? (currently excluded)
|
||||
- Are you writing content/copy? (currently excluded)
|
||||
- Are you doing SEO beyond basics? (currently excluded)
|
||||
- Any special exclusions for this client?
|
||||
|
||||
Why this matters:
|
||||
Clear exclusions prevent scope creep and set expectations.
|
||||
|
||||
Action needed:
|
||||
Review and adjust the exclusions list to match what you will/won't do.
|
||||
|
||||
|
||||
6. CLIENT INFORMATION
|
||||
Location in contract: Throughout, especially signature block
|
||||
|
||||
Questions:
|
||||
- What is the client's legal business name? (shown as "HomeProz" currently)
|
||||
- Who is the signing authority?
|
||||
- What is their title?
|
||||
- Do they have a business entity (LLC, Inc, etc.)?
|
||||
|
||||
Action needed:
|
||||
Get proper legal name and signing authority information.
|
||||
|
||||
|
||||
STRUCTURAL OBSERVATIONS AND FEEDBACK
|
||||
=====================================
|
||||
|
||||
What's working well:
|
||||
--------------------
|
||||
1. Contract uses proven legal language from your successful Landproz contracts
|
||||
2. All standard clauses are present (IP, warranty, liability, etc.)
|
||||
3. Structure is clear and readable
|
||||
4. Appropriate for a mid-size project ($7,000 / 40 hours)
|
||||
5. Fixed-fee with clear change order process at $250/hour
|
||||
6. Standard 60-day warranty period
|
||||
7. Minnesota governing law (consistent with your business)
|
||||
|
||||
Areas that need your input:
|
||||
---------------------------
|
||||
1. Specific deliverables (too generic currently)
|
||||
2. Timeline dates (all marked [INSERT DATE])
|
||||
3. Payment structure decision
|
||||
4. Hosting responsibilities
|
||||
5. High-level project description
|
||||
|
||||
|
||||
RECOMMENDATIONS FOR NEXT STEPS
|
||||
===============================
|
||||
|
||||
Immediate (Before Client Sees Contract):
|
||||
-----------------------------------------
|
||||
1. Gather your project notes about what HomeProz needs
|
||||
- Review any emails, conversations, or notes from client
|
||||
- List specific features and pages they've requested
|
||||
- Clarify any assumptions you've made
|
||||
|
||||
2. Fill in all [INSERT] placeholders:
|
||||
- PROJECT OVERVIEW: High-level description
|
||||
- PROJECT DELIVERABLES: Specific pages, features, functionality
|
||||
- CLIENT RESPONSIBILITIES: What they must provide
|
||||
- TIMELINE: Specific dates
|
||||
- BUDGET: Choose payment structure
|
||||
- All other marked sections
|
||||
|
||||
3. Verify the 40-hour estimate is still accurate
|
||||
- Review deliverables after you fill them in
|
||||
- Adjust total if needed (impacts the $7,000 total)
|
||||
- Consider complexity of custom features
|
||||
|
||||
4. Review exclusions section
|
||||
- Make sure nothing you're planning to do is excluded
|
||||
- Add any specific exclusions for this project
|
||||
- Remove irrelevant exclusions
|
||||
|
||||
5. Proofread for consistency
|
||||
- Make sure "HomeProz" vs "HomeProz.com" is consistent
|
||||
- Check that timeline math works (weeks, dates)
|
||||
- Verify payment amounts are correct
|
||||
|
||||
Before Sending to Client:
|
||||
--------------------------
|
||||
1. Do a final read-through as if you were the client
|
||||
- Is anything confusing or ambiguous?
|
||||
- Are deliverables clear and specific?
|
||||
- Would you sign this if you were them?
|
||||
|
||||
2. Consider adding:
|
||||
- A brief introduction/cover letter
|
||||
- Your contact information clearly listed
|
||||
- Instructions for signing (DocuSign, PDF, printed copy?)
|
||||
- Timeline for them to review and sign
|
||||
|
||||
3. Prepare for questions:
|
||||
- Client may want to negotiate payment terms
|
||||
- Client may request additional features
|
||||
- Have a plan for how to handle change requests
|
||||
|
||||
After Client Review:
|
||||
--------------------
|
||||
1. Be prepared to revise deliverables based on their feedback
|
||||
2. Document any verbal agreements in writing via email
|
||||
3. Don't start work until contract is signed and initial payment received (if using Option A)
|
||||
4. Create a project folder structure for HomeProz work
|
||||
5. Set up project management (tasks, timeline tracking)
|
||||
|
||||
|
||||
CONTRACT STRUCTURE COMPARISON WITH REFERENCES
|
||||
==============================================
|
||||
|
||||
Your draft follows the "Whitelabel Proposal 2025" format:
|
||||
- Single document with all terms
|
||||
- Deliverables-focused approach
|
||||
- Fixed fee pricing
|
||||
- Comprehensive legal section at end
|
||||
|
||||
This is appropriate for this project because:
|
||||
- 40-hour scope is mid-size (between 2023's 180 hours and whitelabel's 60 hours)
|
||||
- Client likely prefers one document vs proposal + SOW
|
||||
- WordPress focus similar to whitelabel project
|
||||
- Fixed fee reduces billing complexity
|
||||
|
||||
Alternative approach (not recommended for this project):
|
||||
- Separate "Project Proposal" + "Statement of Work" like 2023 auction project
|
||||
- More formal, better for very large projects (100+ hours)
|
||||
- Takes longer to prepare and review
|
||||
- Unnecessarily complex for a website build
|
||||
|
||||
|
||||
LEGAL CLAUSE ANALYSIS
|
||||
======================
|
||||
|
||||
All essential clauses are included:
|
||||
✓ Independent contractor status
|
||||
✓ Governing law (Minnesota)
|
||||
✓ Intellectual property and work product ownership
|
||||
✓ Warranty (60 days)
|
||||
✓ Limitation of liability
|
||||
✓ Indemnification
|
||||
✓ Change requests process
|
||||
✓ Confidentiality
|
||||
✓ Entire agreement
|
||||
✓ Severability
|
||||
✓ Termination
|
||||
✓ Payment terms
|
||||
|
||||
Enhanced clauses (improvements over older contracts):
|
||||
✓ Developer Tools license (allows you to reuse frameworks/libraries)
|
||||
✓ Detailed warranty exclusions (protects you from third-party issues)
|
||||
✓ Client content indemnification (protects you from their copyright violations)
|
||||
✓ Portfolio rights (allows you to showcase the work)
|
||||
✓ Termination and refund provisions (fair to both parties)
|
||||
|
||||
These enhancements came from the 2025 whitelabel contract and strengthen
|
||||
your position while remaining fair to the client.
|
||||
|
||||
|
||||
BUSINESS ENTITY UPDATE NEEDED
|
||||
==============================
|
||||
|
||||
IMPORTANT: Your business structure changed in 2024.
|
||||
|
||||
Old: Hansonxyz LLC
|
||||
New: Hanson.xyz (S-Corporation)
|
||||
|
||||
The draft contract uses "Hanson.xyz" throughout, which is correct for 2025.
|
||||
|
||||
However, verify:
|
||||
- Is the legal entity name exactly "Hanson.xyz"?
|
||||
- Or is it "Hanson.xyz, Inc." or "Hanson.xyz Corporation"?
|
||||
- Check your formation documents to use the precise legal name
|
||||
|
||||
In signature block, the contract shows:
|
||||
"FOR HANSON.XYZ:"
|
||||
"Printed Name: Brian Hanson"
|
||||
"Title: Owner"
|
||||
|
||||
Consider if title should be:
|
||||
- "Owner" (general term)
|
||||
- "President" (formal corporate title)
|
||||
- "Principal" (professional services term)
|
||||
|
||||
Check your S-Corp formation documents for your official title.
|
||||
|
||||
|
||||
RATE COMPARISON
|
||||
===============
|
||||
|
||||
Your rates in contracts:
|
||||
- Standard hourly: $175/hour (from CLAUDE.md)
|
||||
- Change orders: $250/hour (from contracts)
|
||||
- This contract: Fixed $7,000 (40 hours × $175 = $7,000)
|
||||
|
||||
The $250/hour change order rate is 43% higher than standard rate.
|
||||
This is intentional and serves to:
|
||||
- Discourage scope creep
|
||||
- Compensate for disruption to planned work
|
||||
- Reflect the premium nature of rush/unplanned work
|
||||
|
||||
This is consistent across all reviewed contracts and should be maintained.
|
||||
|
||||
|
||||
RISK MITIGATION OBSERVATIONS
|
||||
=============================
|
||||
|
||||
The contract includes good risk mitigation:
|
||||
|
||||
1. Limited liability (capped at contract value)
|
||||
- Protects you from catastrophic claims
|
||||
- Standard in professional services contracts
|
||||
|
||||
2. No guarantee of timeline
|
||||
- "Reasonable effort" language
|
||||
- Protects you from client delays
|
||||
- Client can terminate if unreasonably late
|
||||
|
||||
3. Third-party disclaimer
|
||||
- Not liable for WordPress core, plugins, hosting
|
||||
- Important given WordPress ecosystem dependencies
|
||||
|
||||
4. Content indemnification
|
||||
- Client warrants they own/license all content
|
||||
- Protects you from copyright claims
|
||||
|
||||
5. Change order process
|
||||
- All changes must be in writing
|
||||
- Prevents verbal scope creep
|
||||
- Clear pricing for additions
|
||||
|
||||
6. Warranty limitations
|
||||
- 60 days for bugs in YOUR code
|
||||
- Excludes client changes, third-party issues
|
||||
- Standard and reasonable
|
||||
|
||||
Areas to watch:
|
||||
- If client requests reduced liability cap, consult attorney
|
||||
- If client requests extended warranty, charge more
|
||||
- If client removes indemnification, do not accept
|
||||
|
||||
|
||||
WORDPRESS-SPECIFIC CONSIDERATIONS
|
||||
==================================
|
||||
|
||||
Things to clarify for WordPress projects:
|
||||
|
||||
1. Theme approach:
|
||||
- Custom theme from scratch?
|
||||
- Premium theme customization?
|
||||
- Child theme of existing theme?
|
||||
|
||||
Draft assumes custom work, adjust if using premium theme.
|
||||
|
||||
2. Plugins:
|
||||
- Which plugins will you use?
|
||||
- Are plugin licenses included in $7,000?
|
||||
- Who maintains plugin updates after launch?
|
||||
|
||||
Consider listing key plugins in deliverables.
|
||||
|
||||
3. WordPress maintenance:
|
||||
- Is ongoing maintenance included?
|
||||
- Draft excludes it, but clarify
|
||||
- Consider separate maintenance agreement
|
||||
|
||||
Recommend separate monthly maintenance contract.
|
||||
|
||||
4. Training:
|
||||
- Draft includes 1-hour training
|
||||
- Is this enough for their technical level?
|
||||
- Consider video documentation
|
||||
|
||||
Adjust based on client's WordPress experience.
|
||||
|
||||
5. Hosting:
|
||||
- WordPress-optimized hosting recommended
|
||||
- Draft allows for client-provided or you setup
|
||||
- Clarify server requirements
|
||||
|
||||
If they have existing host, verify it meets WordPress requirements.
|
||||
|
||||
|
||||
COMPARISON: YOUR CONTRACTS OVER TIME
|
||||
=====================================
|
||||
|
||||
2023 Auction Project:
|
||||
- $36,000 total
|
||||
- 180 hours estimated
|
||||
- Effective rate: $200/hour
|
||||
- Payment: $12k upfront (33%), $24k on completion
|
||||
- Format: Separate proposal + SOW
|
||||
|
||||
2025 Whitelabel Project:
|
||||
- $10,500 total
|
||||
- 60 hours estimated
|
||||
- Effective rate: $175/hour (described as "discounted")
|
||||
- Payment: Full invoice on delivery, net 30
|
||||
- Format: Combined proposal
|
||||
- Very detailed feature list
|
||||
|
||||
2025 HomeProz (Draft):
|
||||
- $7,000 total
|
||||
- 40 hours estimated
|
||||
- Effective rate: $175/hour
|
||||
- Payment: [TBD - options provided]
|
||||
- Format: Combined proposal (following whitelabel pattern)
|
||||
|
||||
Pattern observations:
|
||||
- Rate has decreased from $200 to $175/hour
|
||||
- Smaller projects = combined format
|
||||
- Payment timing varies by project size
|
||||
- Legal language has gotten more sophisticated
|
||||
- Whitelabel format is cleaner and more professional
|
||||
|
||||
Recommendation:
|
||||
The HomeProz draft appropriately follows the whitelabel format and rate
|
||||
structure. The $175/hour rate is consistent with your current standard.
|
||||
|
||||
|
||||
FINAL CHECKLIST BEFORE SENDING TO CLIENT
|
||||
=========================================
|
||||
|
||||
Content completeness:
|
||||
□ Project description is specific and accurate
|
||||
□ All deliverables are clearly listed
|
||||
□ All exclusions are clearly listed
|
||||
□ Timeline has real dates, not placeholders
|
||||
□ Payment structure is chosen and amounts are correct
|
||||
□ Client responsibilities are clear
|
||||
□ All [INSERT] placeholders are removed
|
||||
|
||||
Legal and business:
|
||||
□ Business entity name is correct (Hanson.xyz)
|
||||
□ Client business name is correct
|
||||
□ Governing law is correct (Minnesota)
|
||||
□ Signature block is complete
|
||||
□ Date field is present
|
||||
□ Your title is correct
|
||||
|
||||
Technical accuracy:
|
||||
□ 40-hour estimate still accurate after filling in deliverables
|
||||
□ Timeline is realistic (not too aggressive)
|
||||
□ Hosting responsibilities are clear
|
||||
□ WordPress-specific details are included
|
||||
□ Plugin/theme approach is specified
|
||||
|
||||
Risk management:
|
||||
□ Warranty terms are acceptable to you
|
||||
□ Liability limitations are in place
|
||||
□ Indemnification is mutual
|
||||
□ Change order process is clear
|
||||
□ Portfolio rights are included
|
||||
|
||||
Professionalism:
|
||||
□ Document is proofread for typos
|
||||
□ Formatting is consistent
|
||||
□ Language is clear and not confusing
|
||||
□ Tone is professional but friendly
|
||||
□ Contact information is included
|
||||
|
||||
|
||||
SUGGESTED NEXT CONVERSATION WITH CLIENT
|
||||
========================================
|
||||
|
||||
Before finalizing contract, have a discussion to nail down:
|
||||
|
||||
1. "Walk me through your vision for the website"
|
||||
- Get them talking about specific pages, features, goals
|
||||
- Listen for scope items you might have missed
|
||||
- Ask about their target audience
|
||||
|
||||
2. "What content do you already have?"
|
||||
- Text, images, logos, brand guidelines
|
||||
- Will they write content or need help?
|
||||
- Photo licensing - do they have rights to images?
|
||||
|
||||
3. "When do you need this launched?"
|
||||
- Specific date or general timeframe?
|
||||
- Are there business events/seasons to consider?
|
||||
- Can they commit to feedback turnaround times?
|
||||
|
||||
4. "Tell me about your hosting situation"
|
||||
- Do they have hosting already?
|
||||
- Do they want you to recommend/set up hosting?
|
||||
- Who will manage hosting long-term?
|
||||
|
||||
5. "What happens after launch?"
|
||||
- Do they want ongoing support/maintenance?
|
||||
- Will they manage content updates themselves?
|
||||
- Are there future phases/features planned?
|
||||
|
||||
Document everything from this conversation and use it to fill in the
|
||||
contract placeholders.
|
||||
|
||||
|
||||
ALTERNATIVE: SCOPE DISCOVERY DOCUMENT FIRST
|
||||
============================================
|
||||
|
||||
Consider creating a separate "Project Scope Discovery" document before
|
||||
finalizing the contract:
|
||||
|
||||
Benefits:
|
||||
- Helps client think through what they really need
|
||||
- Surfaces assumptions and misunderstandings early
|
||||
- Makes contract creation easier (just transfer from discovery doc)
|
||||
- Shows professionalism and thoroughness
|
||||
- Reduces revisions to contract
|
||||
|
||||
Simple discovery document outline:
|
||||
1. Business goals for the website
|
||||
2. Target audience
|
||||
3. Specific pages needed
|
||||
4. Specific features needed
|
||||
5. Design preferences
|
||||
6. Content status (have it / need help)
|
||||
7. Hosting preferences
|
||||
8. Timeline requirements
|
||||
9. Budget parameters
|
||||
10. Success criteria
|
||||
|
||||
This could be a 1-2 page questionnaire or a structured conversation.
|
||||
|
||||
|
||||
RECOMMENDATIONS SUMMARY
|
||||
=======================
|
||||
|
||||
HIGH PRIORITY:
|
||||
1. Collect your project notes on what HomeProz needs
|
||||
2. Fill in all [INSERT] placeholders with specifics
|
||||
3. Choose payment structure (recommend Option A: split payment)
|
||||
4. Set realistic timeline dates
|
||||
5. Verify 40-hour estimate matches actual deliverables
|
||||
|
||||
MEDIUM PRIORITY:
|
||||
6. Clarify hosting responsibilities
|
||||
7. Review and adjust exclusions list
|
||||
8. Verify client's legal business name
|
||||
9. Consider scope discovery conversation first
|
||||
10. Proofread entire document
|
||||
|
||||
LOW PRIORITY:
|
||||
11. Format for professional presentation when moving to Word
|
||||
12. Prepare cover letter or introduction
|
||||
13. Decide on signing method (DocuSign, PDF, print)
|
||||
14. Set up project folder structure
|
||||
15. Plan project kickoff meeting
|
||||
|
||||
The contract framework is solid. The key work now is making it specific to
|
||||
the HomeProz project with accurate deliverables, timeline, and scope.
|
||||
+406
@@ -0,0 +1,406 @@
|
||||
HOMEPROZ CONTRACT - FINAL DECISIONS AND REMAINING TASKS
|
||||
========================================================
|
||||
Date: October 29, 2025
|
||||
|
||||
|
||||
DECISIONS LOCKED IN
|
||||
===================
|
||||
|
||||
1. ACF Pro License
|
||||
DECISION: Managed by Hanson.xyz
|
||||
- License included in development cost
|
||||
- Annual renewal ($49/year) billed as part of hosting fee
|
||||
- Updated in contract: Lines 66-67, 270, 275
|
||||
|
||||
2. Hosting Billing
|
||||
DECISION: Annual billing only
|
||||
- $600/year billed annually
|
||||
- No monthly billing option
|
||||
- Updated in contract: Line 263, 283
|
||||
|
||||
3. Timeline
|
||||
DECISION: 3-4 week queue is firm, non-negotiable
|
||||
- Current commitments must complete first
|
||||
- No rush fee option available
|
||||
- Updated in contract: Lines 222-224
|
||||
|
||||
4. Pricing
|
||||
DECISION: $6,000 development cost is firm
|
||||
- Fixed fee, non-negotiable
|
||||
- No phased approach alternatives
|
||||
- Updated in contract: Lines 239, 253-254
|
||||
|
||||
5. MLS Integration
|
||||
DECISION: Manual entry only, clearly scoped
|
||||
- MLS number field for manual entry
|
||||
- Full automated IDX explicitly excluded
|
||||
- Separate future project if desired
|
||||
- Updated in contract: Lines 78-86
|
||||
|
||||
6. Email Migration
|
||||
DECISION: 2 hours included, no special considerations
|
||||
- Client relationship understood
|
||||
- Complexity expected to be manageable
|
||||
- No changes needed to contract
|
||||
|
||||
|
||||
CONTRACT UPDATES COMPLETED
|
||||
===========================
|
||||
|
||||
Section: Advanced Custom Fields Implementation
|
||||
- Added: "ACF Pro license ($49/year) included in development cost and managed
|
||||
by Developer (annual renewal billed as part of ongoing hosting/support)"
|
||||
|
||||
Section: MLS Integration
|
||||
- Changed title from "MLS Integration Planning" to "MLS Integration - Manual Entry"
|
||||
- Added: "This is manual entry only; full automated IDX integration with property
|
||||
import/sync is NOT included and would be a separate future project if desired"
|
||||
- Clarified scope is MLS number field only
|
||||
|
||||
Section: Timeline
|
||||
- Added: "The 3-4 week pre-development period is necessary due to existing
|
||||
project commitments (Auction Cast, Kodex, and Ascent websites) and cannot
|
||||
be accelerated."
|
||||
- Removed any language suggesting rush fees or timeline flexibility
|
||||
|
||||
Section: Budget - Development
|
||||
- Added: "This price is firm and non-negotiable."
|
||||
- Changed from "$7,000" to "$6,000 (fixed fee)" for absolute clarity
|
||||
|
||||
Section: Budget - Hosting
|
||||
- Changed from "$600 per year" to "$600 per year (billed annually)"
|
||||
- Added: "(Equivalent to $50/month, but billed once per year for administrative
|
||||
simplicity)"
|
||||
- Added to included items: "WordPress core, theme, and plugin updates (including
|
||||
ACF Pro license renewal)"
|
||||
- Added to included items: "ACF Pro plugin license maintenance and annual renewal"
|
||||
- Added: "Billing is annual only; monthly billing is not available for this service"
|
||||
|
||||
|
||||
REMAINING TASKS BEFORE SENDING TO CLIENT
|
||||
=========================================
|
||||
|
||||
CRITICAL - MUST COMPLETE:
|
||||
-------------------------
|
||||
|
||||
1. [ ] INSERT CONTRACT SIGNING DATE
|
||||
Location: Line 4 and line 211
|
||||
Action: Replace "[INSERT DATE]" with actual/proposed signing date
|
||||
Recommendation: Use date you plan to send contract, or "TBD upon agreement"
|
||||
|
||||
2. [ ] INSERT MILESTONE DATES
|
||||
Location: Lines 211-219
|
||||
Current placeholders:
|
||||
- Contract signing: [INSERT DATE]
|
||||
- Development start: [INSERT DATE] (should be 3-4 weeks after signing)
|
||||
- Client review: [INSERT DATE] (1 week after dev start)
|
||||
- Final delivery: [INSERT DATE] (4-5 weeks after signing)
|
||||
- Training: [INSERT DATE] (week of launch)
|
||||
|
||||
Action: Either insert specific dates or change to:
|
||||
"- Contract signing: [Date of execution]
|
||||
- Development start: 3-4 weeks after signing
|
||||
- Client review: 1 week after development start
|
||||
- Final delivery: 4-5 weeks after contract signing
|
||||
- Training session: Week of launch"
|
||||
|
||||
3. [ ] CONFIRM CLIENT LEGAL BUSINESS NAME
|
||||
Current: "HomeProz" throughout contract
|
||||
Action: Verify with Dayna exact legal entity name
|
||||
Possibilities:
|
||||
- HomeProz (if sole proprietorship or DBA)
|
||||
- HomeProz LLC
|
||||
- HomeProz, Inc.
|
||||
- Different legal entity entirely
|
||||
|
||||
Replace throughout contract once confirmed
|
||||
|
||||
4. [ ] GET CLIENT CONTACT INFORMATION
|
||||
Needed for contract:
|
||||
- Legal business name (see above)
|
||||
- Signing authority name and title
|
||||
- Business address (for signature block)
|
||||
- Email for invoices
|
||||
- Phone number
|
||||
|
||||
5. [ ] FORMAT CONTRACT FOR PRESENTATION
|
||||
Current: Plain text .txt file
|
||||
Needs: Professional Word document formatting
|
||||
Action: Convert to .docx with:
|
||||
- Professional font (Arial, Calibri, or Times New Roman)
|
||||
- Clear section headings with formatting
|
||||
- Consistent spacing
|
||||
- Signature blocks at end with lines for signatures
|
||||
- Page numbers
|
||||
- Header/footer with "HomeProz Website Development Agreement"
|
||||
|
||||
|
||||
OPTIONAL BUT RECOMMENDED:
|
||||
-------------------------
|
||||
|
||||
6. [ ] CREATE COVER LETTER/EMAIL
|
||||
Include:
|
||||
- Brief project summary
|
||||
- Total first year investment ($6,600)
|
||||
- Timeline overview (4-5 weeks)
|
||||
- What you need from them (review, sign, payment)
|
||||
- Deadline for review (suggest 5-7 business days)
|
||||
- Your contact information for questions
|
||||
|
||||
7. [ ] PREPARE INVOICE TEMPLATE
|
||||
For initial $2,000 payment
|
||||
Ready to send upon contract signing
|
||||
Include:
|
||||
- Invoice number
|
||||
- Date
|
||||
- Payment terms
|
||||
- Payment methods/instructions
|
||||
- Due date (immediately upon signing)
|
||||
|
||||
8. [ ] SET UP PROJECT FOLDER
|
||||
Create: Clients/HomeProz/Projects/WordPress-Website/
|
||||
Subfolders:
|
||||
- Design/ (for mockups, assets)
|
||||
- Development/ (for code, staging)
|
||||
- Content/ (for client-provided content)
|
||||
- Training/ (for documentation)
|
||||
- Correspondence/ (for emails, meeting notes)
|
||||
|
||||
9. [ ] CALENDAR PLANNING
|
||||
Block out:
|
||||
- Week of [dev start date]: HomeProz development sprint
|
||||
- [Training date]: HomeProz training session
|
||||
- [Launch date]: HomeProz launch and go-live
|
||||
|
||||
This reserves time and prevents overbooking
|
||||
|
||||
10. [ ] PREPARE KICKOFF MEETING AGENDA
|
||||
For when development starts:
|
||||
- Review project scope
|
||||
- Confirm deliverables
|
||||
- Review ACF field structure
|
||||
- Gather any remaining requirements
|
||||
- Set communication cadence
|
||||
- Answer questions
|
||||
|
||||
|
||||
QUALITY CHECKS BEFORE SENDING
|
||||
==============================
|
||||
|
||||
Review Contract For:
|
||||
--------------------
|
||||
□ All [INSERT] placeholders are filled or removed
|
||||
□ Client legal name is correct throughout
|
||||
□ Pricing totals are correct ($6,000 + $600 = $6,600)
|
||||
□ Timeline is realistic based on your actual availability
|
||||
□ Scope matches what was discussed in meeting
|
||||
□ Exclusions don't exclude something you plan to do
|
||||
□ All dates are consistent and make sense
|
||||
□ Professional tone throughout
|
||||
□ No typos or grammatical errors
|
||||
□ Signature blocks are complete with space for signatures
|
||||
□ All standard legal clauses are present
|
||||
□ Payment terms are clear
|
||||
□ Your business name (Hanson.xyz) is correct everywhere
|
||||
|
||||
|
||||
SENDING CHECKLIST
|
||||
=================
|
||||
|
||||
When ready to send:
|
||||
-------------------
|
||||
□ Contract formatted as professional Word document
|
||||
□ Cover email drafted and reviewed
|
||||
□ Invoice template ready to send upon signing
|
||||
□ Calendar blocked for development time
|
||||
□ Project folder structure created
|
||||
□ Client contact information confirmed
|
||||
□ You've read through contract one final time as if you're the client
|
||||
□ You're prepared to answer questions about scope, timeline, pricing
|
||||
|
||||
|
||||
INTERVIEW APPROACH
|
||||
==================
|
||||
|
||||
Since you know the client (Dayna Gottberg) and have already had initial
|
||||
discussions, the "interview" may be more informal. Suggested approach:
|
||||
|
||||
EMAIL FIRST:
|
||||
Send brief email saying:
|
||||
"Hi Dayna,
|
||||
|
||||
I'm putting together the contract for the HomeProz website project. Before
|
||||
I finalize it, I need to confirm a few details:
|
||||
|
||||
1. What is the legal business name for HomeProz? (HomeProz LLC? Inc.? Other?)
|
||||
2. Who will be signing the contract? (Name and title)
|
||||
3. What's the best email for invoices?
|
||||
4. Do you have the HomeProz logo in digital format? If so, what formats?
|
||||
5. When would you ideally like to launch the site?
|
||||
|
||||
Once I have these details, I'll send over the complete contract for your review.
|
||||
|
||||
Thanks,
|
||||
Brian"
|
||||
|
||||
THEN CALL/MEETING IF NEEDED:
|
||||
If response raises questions or concerns, schedule call to discuss:
|
||||
- Budget confirmation
|
||||
- Timeline expectations
|
||||
- Scope clarification
|
||||
- Any additional questions
|
||||
|
||||
This approach is more efficient than comprehensive interview since you already
|
||||
have good understanding from previous meeting.
|
||||
|
||||
|
||||
ANTICIPATED CLIENT QUESTIONS
|
||||
=============================
|
||||
|
||||
Be prepared to answer:
|
||||
|
||||
"Can we do monthly billing on hosting instead of annual?"
|
||||
ANSWER: "I've structured it as annual billing for administrative efficiency.
|
||||
The total is the same ($600/year vs $50/month), but annual billing reduces
|
||||
invoice overhead for both of us. This is standard for my hosting clients."
|
||||
|
||||
"What if we need more than 2 hours of email migration help?"
|
||||
ANSWER: "Based on our previous discussions, I expect 2 hours will be
|
||||
sufficient for your setup. If it turns out to be more complex, any additional
|
||||
time would be billed at $175/hour, but I'll let you know before exceeding
|
||||
the included time."
|
||||
|
||||
"Can you start sooner than 3-4 weeks?"
|
||||
ANSWER: "Unfortunately no - I have committed deliverables for Auction Cast,
|
||||
Kodex, and Ascent that I need to complete first. The 3-4 week timeline is
|
||||
firm. However, this gives you time to gather all the content, branding assets,
|
||||
and other materials we'll need, so we can hit the ground running when
|
||||
development starts."
|
||||
|
||||
"Can we do this in phases to reduce upfront cost?"
|
||||
ANSWER: "The $6,000 is already a discounted rate for startups ($150/hour vs
|
||||
my standard $175/hour). The project scope is defined as a complete deliverable.
|
||||
The payment structure does split it - $2,000 upfront and $4,000 on completion
|
||||
- which helps with cashflow."
|
||||
|
||||
"What if we want to add features later?"
|
||||
ANSWER: "Absolutely - this contract covers the initial website build. After
|
||||
launch, we can discuss additional features like full IDX integration, advanced
|
||||
search, lead capture systems, etc. Those would be quoted separately, likely
|
||||
on an hourly basis at $175/hour or as a new fixed-fee project depending on
|
||||
scope."
|
||||
|
||||
"Is the $600/year hosting required?"
|
||||
ANSWER: "Yes - the website will be built on my managed hosting infrastructure,
|
||||
and the hosting fee covers not just server space but active management:
|
||||
daily backups, security monitoring, WordPress updates, plugin maintenance
|
||||
including the ACF Pro license, and up to 2 hours per month of technical
|
||||
support. This ensures the site stays secure, fast, and functional long-term."
|
||||
|
||||
|
||||
POST-CONTRACT EXECUTION PLAN
|
||||
=============================
|
||||
|
||||
After contract is signed and initial payment received:
|
||||
|
||||
Week 0 (Immediately):
|
||||
- Send payment confirmation
|
||||
- Request all client materials (logo, content, access credentials)
|
||||
- Set up staging environment
|
||||
- Purchase/activate ACF Pro license
|
||||
- Add project to task list
|
||||
|
||||
Weeks 1-3 (Queue Period):
|
||||
- Weekly check-in email to client on queue status
|
||||
- Complete Auction Cast, Kodex, Ascent projects
|
||||
- Prepare development environment
|
||||
- Review client-provided materials as they come in
|
||||
- Flag any missing materials or questions
|
||||
|
||||
Week 4 (Development Week):
|
||||
- Kickoff meeting Monday
|
||||
- Development Days 1-5
|
||||
- Client review on staging Thursday/Friday
|
||||
- Gather feedback
|
||||
|
||||
Week 5 (Finalization):
|
||||
- Implement client feedback
|
||||
- Final QA testing
|
||||
- Training session
|
||||
- Launch to production
|
||||
- Email migration (if applicable)
|
||||
- Post-launch verification
|
||||
|
||||
Week 5+60 days (Warranty Period):
|
||||
- Monitor for issues
|
||||
- Quick response to any bugs or problems
|
||||
- No charge for fixes to delivered functionality
|
||||
|
||||
Ongoing:
|
||||
- Annual hosting management
|
||||
- ACF Pro license renewals
|
||||
- Potential future enhancement projects
|
||||
|
||||
|
||||
SUCCESS METRICS
|
||||
===============
|
||||
|
||||
This project is successful if:
|
||||
|
||||
✓ Contract signed and initial payment received
|
||||
✓ Development starts on schedule (3-4 weeks after signing)
|
||||
✓ Launches within 4-5 weeks total from signing
|
||||
✓ Client can independently add/manage property listings via ACF
|
||||
✓ Site is responsive, fast, secure, and professional
|
||||
✓ All deliverables completed as specified
|
||||
✓ Training is effective (client feels confident)
|
||||
✓ Client is satisfied with final product
|
||||
✓ Hosting relationship continues beyond Year 1
|
||||
✓ Referrals or future projects from this relationship
|
||||
|
||||
|
||||
NEXT IMMEDIATE ACTION
|
||||
=====================
|
||||
|
||||
Your next step should be:
|
||||
|
||||
1. Send brief email to Dayna requesting:
|
||||
- Legal business name
|
||||
- Signing authority
|
||||
- Logo/branding assets
|
||||
- Preferred launch timeframe
|
||||
|
||||
2. Once you receive response:
|
||||
- Update contract with legal business name
|
||||
- Insert realistic dates based on response
|
||||
- Format contract to Word document
|
||||
- Send contract with cover letter for review
|
||||
|
||||
3. While client reviews:
|
||||
- Prepare invoice for $2,000 initial payment
|
||||
- Set up project folder structure
|
||||
- Block calendar for development time
|
||||
- Begin gathering any technical requirements
|
||||
|
||||
|
||||
DOCUMENT STATUS
|
||||
===============
|
||||
|
||||
Contract Document:
|
||||
✓ All your decisions incorporated
|
||||
✓ Scope clearly defined
|
||||
✓ Pricing locked at $6,000 + $600 = $6,600
|
||||
✓ Timeline set at 3-4 weeks queue + 1 week dev
|
||||
✓ MLS scoped as manual only
|
||||
✓ ACF Pro license included and managed by you
|
||||
✓ Annual billing only
|
||||
✓ All standard legal clauses present
|
||||
|
||||
Remaining before client-ready:
|
||||
- Insert dates (or make dates relative to signing)
|
||||
- Confirm client legal business name
|
||||
- Format to Word document
|
||||
- Final proofread
|
||||
- Create cover email
|
||||
|
||||
Current Status: 95% complete, ready for final details and formatting
|
||||
@@ -0,0 +1,603 @@
|
||||
HOMEPROZ CONTRACT INTERVIEW QUESTIONS
|
||||
======================================
|
||||
Date: October 29, 2025
|
||||
|
||||
Purpose: Gather information needed to finalize contract and ensure accurate scope
|
||||
|
||||
|
||||
INSTRUCTIONS FOR INTERVIEW
|
||||
===========================
|
||||
|
||||
These questions are organized by priority and topic. You don't need to ask all
|
||||
questions in order - use your judgment based on conversation flow. The most
|
||||
critical questions are marked [CRITICAL].
|
||||
|
||||
Take notes during the conversation and use responses to fill in contract
|
||||
placeholders and adjust scope as needed.
|
||||
|
||||
|
||||
SECTION 1: BUDGET AND PAYMENT
|
||||
==============================
|
||||
|
||||
[CRITICAL] Q1.1: Budget Confirmation
|
||||
"I've drafted a proposal showing $6,000 for website development and $600 for
|
||||
the first year of managed hosting, for a total first-year investment of $6,600.
|
||||
Is this within your budget?"
|
||||
|
||||
Follow-up if yes:
|
||||
- Confirm payment schedule: $2,000 upfront, $4,000 on completion acceptable?
|
||||
|
||||
Follow-up if budget is tight:
|
||||
- Would you prefer a phased approach? (basic site first, then add features)
|
||||
- Would monthly payment plan help? ($500/month for 12 months plus hosting?)
|
||||
- Which features are must-have vs nice-to-have?
|
||||
|
||||
[CRITICAL] Q1.2: Hosting Billing Preference
|
||||
"For hosting, I've proposed annual billing at $600/year, but I can also do
|
||||
monthly at $50/month. Which would you prefer?"
|
||||
|
||||
Note the difference:
|
||||
- Annual: One invoice per year, $600 total
|
||||
- Monthly: 12 invoices per year, $50 each = $600 total
|
||||
|
||||
[CRITICAL] Q1.3: Ongoing Cost Acceptance
|
||||
"Beyond the website development, there are ongoing annual costs:
|
||||
- Managed hosting: $600/year
|
||||
- MLS subscription (if you choose to use it): $660/year
|
||||
- Google Workspace (if you migrate email): ~$72+/year per user
|
||||
Total recurring: approximately $1,300-2,000/year depending on choices.
|
||||
Are you comfortable with these ongoing costs?"
|
||||
|
||||
Q1.4: ACF Pro License
|
||||
"The Advanced Custom Fields Pro plugin costs $49/year for the license. I can
|
||||
either include this in the development cost and manage renewals for you, or
|
||||
you can purchase it directly in your name and handle renewals yourself. Which
|
||||
would you prefer?"
|
||||
|
||||
Option A: I include it ($6,000 covers it, I handle renewals, bill annually)
|
||||
Option B: You purchase it (your license, your renewal responsibility)
|
||||
|
||||
|
||||
SECTION 2: MLS INTEGRATION SCOPE
|
||||
=================================
|
||||
|
||||
[CRITICAL] Q2.1: MLS Subscription Decision
|
||||
"Are you planning to subscribe to Northstar MLS? This would cost $100 setup
|
||||
plus $55/month ($660/year)."
|
||||
|
||||
If YES, proceed with Q2.2-2.4
|
||||
If NO or UNSURE, skip to Q2.5
|
||||
|
||||
[CRITICAL] Q2.2: MLS Integration Level
|
||||
"For MLS integration, there are different levels of sophistication:
|
||||
|
||||
Option A - Manual MLS Entry ($0 additional, included in base price):
|
||||
- You manually enter the MLS number into a field
|
||||
- Website displays it, but you still enter all property details manually
|
||||
- Simple and included in current scope
|
||||
|
||||
Option B - IDX Property Display ($2,000-3,000 additional, rough estimate):
|
||||
- Properties automatically import from MLS when you enter MLS number
|
||||
- Pulls description, photos, pricing automatically
|
||||
- Requires third-party IDX service (additional monthly fees $50-200/month)
|
||||
- Requires additional development time
|
||||
|
||||
Option C - Full IDX with Search ($5,000-10,000 additional, rough estimate):
|
||||
- Entire MLS database searchable on your site
|
||||
- Automated updates when listings change
|
||||
- Advanced search and filtering
|
||||
- Requires premium IDX service (expensive monthly fees)
|
||||
- Significant additional development
|
||||
|
||||
Which level matches your needs and budget?"
|
||||
|
||||
Q2.3: MLS Property Types
|
||||
"What types of properties will you be listing from MLS?"
|
||||
- Residential only?
|
||||
- Commercial?
|
||||
- Land/lots?
|
||||
- All types?
|
||||
|
||||
Q2.4: MLS vs Custom Listings Ratio
|
||||
"Roughly what percentage of your properties will be:
|
||||
- MLS listings: ____%
|
||||
- Custom/non-MLS listings (commercial, private): ____%"
|
||||
|
||||
This helps determine if MLS integration is worth the cost.
|
||||
|
||||
Q2.5: If Not Using MLS
|
||||
"If you're not using MLS initially, do you want us to plan the site structure
|
||||
so that MLS can be added later without major rework?"
|
||||
|
||||
|
||||
SECTION 3: PROPERTY LISTING REQUIREMENTS
|
||||
=========================================
|
||||
|
||||
Q3.1: Property Fields and Data
|
||||
"Let's talk about what information you need to track for each property. Beyond
|
||||
the basics like address and price, what else do you need?"
|
||||
|
||||
Common fields (confirm which are needed):
|
||||
- Property type (residential, commercial, land)
|
||||
- Price
|
||||
- Bedrooms / Bathrooms
|
||||
- Square footage (living space, lot size)
|
||||
- Year built
|
||||
- Property features (fireplace, garage, pool, etc.)
|
||||
- School district
|
||||
- HOA fees
|
||||
- Tax information
|
||||
- Property status (active, pending, sold, off-market)
|
||||
- Days on market
|
||||
- Open house dates/times
|
||||
- Agent/listing contact information
|
||||
- MLS number
|
||||
- Parcel/tax ID number
|
||||
|
||||
Less common fields (ask if needed):
|
||||
- Virtual tour link
|
||||
- Video tour link
|
||||
- 3D walkthrough
|
||||
- Floor plans
|
||||
- Plat/survey documents
|
||||
- Property disclosures
|
||||
- Financing options
|
||||
- Rental income (for investment properties)
|
||||
- Zoning information (for commercial/land)
|
||||
- Utilities available (for land)
|
||||
- Development rights (for commercial)
|
||||
|
||||
[CRITICAL] Q3.2: Photo Gallery Requirements
|
||||
"How many photos do you typically need per property listing?"
|
||||
- Minimum: ___
|
||||
- Maximum: ___
|
||||
- Average: ___
|
||||
|
||||
"Do you need the ability to:
|
||||
- Reorder photos?
|
||||
- Set a featured/main photo?
|
||||
- Add captions to photos?
|
||||
- Organize photos by room/category?"
|
||||
|
||||
Q3.3: Property Search and Filtering
|
||||
"How do you want visitors to find properties on your site?"
|
||||
|
||||
Basic options (probably needed):
|
||||
- List all properties on one page
|
||||
- Filter by property type (residential, commercial, land)
|
||||
- Filter by price range
|
||||
- Filter by bedrooms/bathrooms
|
||||
- Sort by price, date added, etc.
|
||||
|
||||
Advanced options (ask if desired):
|
||||
- Map-based search
|
||||
- Radius/location search (within X miles of address)
|
||||
- Filter by specific features (pool, garage, etc.)
|
||||
- Saved searches for registered users
|
||||
- Email alerts when matching properties are added
|
||||
|
||||
Q3.4: Featured/Highlighted Properties
|
||||
"Do you want the ability to feature certain properties on the homepage or in
|
||||
special sections?"
|
||||
|
||||
Q3.5: Sold/Past Properties
|
||||
"Do you want to display sold properties as a portfolio/track record, or only
|
||||
show active listings?"
|
||||
|
||||
|
||||
SECTION 4: EMAIL MIGRATION
|
||||
===========================
|
||||
|
||||
[CRITICAL] Q4.1: Current Email Setup
|
||||
"What's your current email situation?"
|
||||
- How many email addresses do you have?
|
||||
- What provider? (GoDaddy, Gmail, other?)
|
||||
- Mailbox sizes? (helps estimate migration time)
|
||||
- Do you need to preserve existing emails or start fresh?
|
||||
|
||||
Q4.2: Google Workspace vs Alternatives
|
||||
"For Gmail, there are a few options:
|
||||
|
||||
Option A - Google Workspace ($6-12/user/month):
|
||||
- Professional email @homeproz.com through Gmail
|
||||
- Includes Google Drive, Calendar, Docs, etc.
|
||||
- Best for business use
|
||||
|
||||
Option B - Gmail Forwarding (free):
|
||||
- Keep email hosted where it is
|
||||
- Forward to personal Gmail accounts
|
||||
- Less professional, but free
|
||||
|
||||
Option C - Keep existing email setup:
|
||||
- No migration needed
|
||||
- May be fine if current setup works
|
||||
|
||||
Which direction are you leaning?"
|
||||
|
||||
Q4.3: Migration Timing
|
||||
"When would you like the email migration to happen?"
|
||||
- During website development?
|
||||
- After website launch?
|
||||
- Separate timeline?
|
||||
|
||||
Note: Contract includes 2 hours of email migration support. Based on Q4.1
|
||||
answers, determine if this is sufficient or if additional hours needed.
|
||||
|
||||
|
||||
SECTION 5: DESIGN AND BRANDING
|
||||
===============================
|
||||
|
||||
[CRITICAL] Q5.1: Existing Design Materials
|
||||
"You mentioned there's an existing HomeProz design aesthetic. Can you show me
|
||||
or send me:
|
||||
- Logo (in vector format if possible: AI, EPS, SVG, or at minimum high-res PNG)
|
||||
- Color scheme / brand colors (hex codes if you have them)
|
||||
- The current GoDaddy splash page
|
||||
- Any other marketing materials, business cards, signage, etc."
|
||||
|
||||
Q5.2: HomeProz vs Landproz Branding
|
||||
"HomeProz is separate from Landproz - does that mean completely different
|
||||
branding, or do they share some visual elements?"
|
||||
|
||||
Q5.3: Design Expectations
|
||||
"For the website design, are you expecting:
|
||||
- A completely custom design from scratch?
|
||||
- Adaptation of the existing splash page design?
|
||||
- A professional but template-based design customized to your brand?
|
||||
- Something similar to another website? (if so, examples help)"
|
||||
|
||||
Q5.4: Design Preferences
|
||||
"Any specific design preferences or requirements?"
|
||||
- Modern/minimalist vs traditional/detailed?
|
||||
- Bright colors vs subdued/professional?
|
||||
- Photo-heavy vs text-focused?
|
||||
- Any websites you like as inspiration?
|
||||
- Any websites you dislike that we should avoid?
|
||||
|
||||
|
||||
SECTION 6: CONTENT AND MIGRATION
|
||||
=================================
|
||||
|
||||
Q6.1: Existing Content
|
||||
"What content exists currently that we can use?"
|
||||
- Company description/about text
|
||||
- Service descriptions
|
||||
- Team member bios
|
||||
- Any existing property listings and photos
|
||||
- Testimonials or reviews
|
||||
- Contact information
|
||||
|
||||
Q6.2: Content Creation Responsibility
|
||||
"For any content that doesn't exist yet, who will write it?"
|
||||
- You'll provide all text?
|
||||
- You need help with copywriting? (would be additional cost)
|
||||
- We can use placeholder text to start?
|
||||
|
||||
Q6.3: Photography
|
||||
"For property photos:
|
||||
- You'll provide all photos?
|
||||
- You have a photographer?
|
||||
- You need stock photos? (some included, specify how many)
|
||||
- For non-property images (team photos, office, etc.), do those exist?"
|
||||
|
||||
Q6.4: Domain and Current Site
|
||||
"Your domain is with GoDaddy currently showing a splash page. Correct?"
|
||||
- Domain name: _____________ (confirm exact spelling)
|
||||
- GoDaddy account access: who has login credentials?
|
||||
- Do you want to keep domain with GoDaddy or transfer to another registrar?
|
||||
- Anything on the splash page you want to preserve?
|
||||
|
||||
|
||||
SECTION 7: USERS AND TRAINING
|
||||
==============================
|
||||
|
||||
Q7.1: Who Will Use the System?
|
||||
"Who will be responsible for managing the website day-to-day?"
|
||||
- How many people?
|
||||
- Names/roles:
|
||||
- _______________ (role: _________)
|
||||
- _______________ (role: _________)
|
||||
|
||||
Q7.2: Technical Skill Level
|
||||
"On a scale of 1-10, how comfortable is your team with technology and websites?"
|
||||
1 = Never used a computer
|
||||
5 = Comfortable with Facebook, email, basic tasks
|
||||
10 = Web developer
|
||||
|
||||
This helps determine training depth and documentation detail needed.
|
||||
|
||||
Q7.3: Training Preferences
|
||||
"For training on how to add and manage property listings, would you prefer:"
|
||||
- In-person session (if local)?
|
||||
- Video call/screen sharing?
|
||||
- Recorded video tutorials you can reference later?
|
||||
- Written documentation?
|
||||
- All of the above?
|
||||
|
||||
Q7.4: Ongoing Support Expectations
|
||||
"After the 60-day warranty period, if you need help or have questions, what
|
||||
would you expect?"
|
||||
- Included in hosting fee (up to 2 hours/month support included)?
|
||||
- Pay-as-you-go at $175/hour?
|
||||
- Monthly retainer for X hours?
|
||||
|
||||
|
||||
SECTION 8: TIMELINE AND URGENCY
|
||||
================================
|
||||
|
||||
[CRITICAL] Q8.1: Launch Urgency
|
||||
"How soon do you need this website live?"
|
||||
- ASAP / urgent business need?
|
||||
- By a specific date? (if so, what date and why?)
|
||||
- Flexible timeline, whenever it's ready?
|
||||
|
||||
Q8.2: Queue Time Acceptance
|
||||
"Based on current commitments (Auction Cast, Kodex, Ascent), I can't start
|
||||
development for 3-4 weeks. Realistically, you're looking at:
|
||||
- Contract signing: [date]
|
||||
- Development start: [date, 3-4 weeks later]
|
||||
- Estimated launch: [date, 4-5 weeks from signing]
|
||||
|
||||
Does this timeline work for you, or is the launch urgency high enough that we
|
||||
need to discuss alternatives?"
|
||||
|
||||
Alternatives if urgent:
|
||||
- Pay rush fee for prioritization (20% additional)?
|
||||
- Reduce scope to launch faster, add features later?
|
||||
- Wait until schedule opens up?
|
||||
|
||||
Q8.3: Content/Asset Provision Timeline
|
||||
"When can you provide:"
|
||||
- Logo and branding assets: ___________
|
||||
- Content/text for pages: ___________
|
||||
- Property listing data for testing: ___________
|
||||
- Access to GoDaddy account: ___________
|
||||
- Any other required materials: ___________
|
||||
|
||||
|
||||
SECTION 9: BUSINESS AND LEGAL
|
||||
==============================
|
||||
|
||||
[CRITICAL] Q9.1: Legal Business Name
|
||||
"For the contract, what is your legal business entity name?"
|
||||
- "HomeProz" exactly?
|
||||
- "HomeProz LLC"?
|
||||
- "HomeProz Inc"?
|
||||
- Operating under a different legal entity?
|
||||
- DBA/doing business as?
|
||||
|
||||
Q9.2: Signing Authority
|
||||
"Who will be signing the contract?"
|
||||
- Name: _______________
|
||||
- Title: _______________
|
||||
- Email: _______________
|
||||
- Phone: _______________
|
||||
|
||||
Q9.3: Billing Information
|
||||
"Where should invoices be sent?"
|
||||
- Email: _______________
|
||||
- Mailing address (if paying by check): _______________
|
||||
- Preferred payment method: _______________
|
||||
|
||||
Q9.4: Business Structure
|
||||
"Just for my records, what type of business entity is HomeProz?"
|
||||
- LLC?
|
||||
- Corporation?
|
||||
- Sole proprietorship?
|
||||
- Partnership?
|
||||
|
||||
Q9.5: Tax ID
|
||||
"Do you have an EIN/Tax ID for the business?"
|
||||
(Needed for proper invoicing if they request it)
|
||||
|
||||
|
||||
SECTION 10: TECHNICAL DETAILS
|
||||
==============================
|
||||
|
||||
Q10.1: Domain Name Confirmation
|
||||
"Confirm exact domain name: _______________"
|
||||
|
||||
Q10.2: Email Addresses Needed
|
||||
"What email addresses do you need set up?"
|
||||
- info@homeproz.com?
|
||||
- [name]@homeproz.com?
|
||||
- List all needed addresses: _______________
|
||||
|
||||
Q10.3: Third-Party Integrations
|
||||
"Are there any other systems or tools you need the website to integrate with?"
|
||||
- CRM system?
|
||||
- Email marketing (Mailchimp, Constant Contact, etc.)?
|
||||
- Social media auto-posting?
|
||||
- Analytics (Google Analytics)?
|
||||
- Other?
|
||||
|
||||
Q10.4: Compliance Requirements
|
||||
"Are there any specific compliance or legal requirements for your industry?"
|
||||
- Fair Housing Act compliance (real estate specific)?
|
||||
- Accessibility standards (ADA/WCAG)?
|
||||
- Privacy policy requirements?
|
||||
- Terms of service?
|
||||
|
||||
I can include basic fair housing and privacy policy templates if needed.
|
||||
|
||||
|
||||
SECTION 11: FUTURE PLANNING
|
||||
============================
|
||||
|
||||
Q11.1: Expected Growth
|
||||
"Thinking ahead:
|
||||
- How many properties do you expect to list in Year 1? ___
|
||||
- How many properties in Year 2-3? ___
|
||||
- How many team members in Year 1? ___
|
||||
- How many team members in Year 2-3? ___"
|
||||
|
||||
This helps plan hosting resources and system scalability.
|
||||
|
||||
Q11.2: Future Features Wishlist
|
||||
"What features might you want to add in the future?"
|
||||
(Helps ensure we build the foundation to support future expansion)
|
||||
|
||||
Common future additions:
|
||||
- Blog for market updates/news
|
||||
- Client portal for buyers/sellers
|
||||
- Document upload/signing
|
||||
- Mortgage calculator
|
||||
- Market statistics/reports
|
||||
- Neighborhood guides
|
||||
- Agent profiles (if growing team)
|
||||
- Office locations map (if multiple offices)
|
||||
|
||||
Q11.3: Success Metrics
|
||||
"How will you measure if this website is successful?"
|
||||
- Number of properties listed?
|
||||
- Lead inquiries per month?
|
||||
- Direct property sales from website?
|
||||
- Professional appearance?
|
||||
- Ease of property management?
|
||||
- Other metrics?
|
||||
|
||||
Understanding success criteria helps ensure we build the right solution.
|
||||
|
||||
|
||||
SECTION 12: LANDPROZ RELATIONSHIP
|
||||
==================================
|
||||
|
||||
Q12.1: Shared Resources
|
||||
"Since HomeProz is separate from Landproz, will there be any shared resources?"
|
||||
- Shared staff?
|
||||
- Shared office?
|
||||
- Shared marketing?
|
||||
- Cross-referrals?
|
||||
- Completely independent?
|
||||
|
||||
Q12.2: System Similarities
|
||||
"Would you like the HomeProz website to work similarly to any Landproz systems,
|
||||
or should it be completely different?"
|
||||
|
||||
This helps determine if we can reuse any patterns or if fresh approach is better.
|
||||
|
||||
|
||||
WRAP-UP QUESTIONS
|
||||
=================
|
||||
|
||||
Q13.1: Questions for Me?
|
||||
"What questions do you have about the proposal, timeline, or process?"
|
||||
|
||||
Q13.2: Concerns or Hesitations?
|
||||
"Is there anything about the project that concerns you or makes you hesitate?"
|
||||
|
||||
Address any concerns directly and honestly.
|
||||
|
||||
Q13.3: Additional Considerations
|
||||
"Is there anything important I haven't asked about that I should know?"
|
||||
|
||||
Q13.4: Next Steps Agreement
|
||||
"If everything looks good, here are the next steps:
|
||||
1. I'll finalize the contract with the details from this conversation
|
||||
2. I'll send you the contract for review
|
||||
3. You review and send back any questions or changes
|
||||
4. We sign the contract
|
||||
5. You send the $2,000 initial payment
|
||||
6. I queue the project to start in 3-4 weeks
|
||||
7. I keep you updated on progress
|
||||
8. We launch in approximately 4-5 weeks total
|
||||
|
||||
Does this process work for you?"
|
||||
|
||||
|
||||
POST-INTERVIEW CHECKLIST
|
||||
=========================
|
||||
|
||||
After the interview, use responses to:
|
||||
|
||||
□ Update contract PROJECT OVERVIEW with accurate description
|
||||
□ Finalize PROJECT DELIVERABLES based on confirmed features
|
||||
□ Adjust EXCLUSIONS based on confirmed scope
|
||||
□ Update CLIENT RESPONSIBILITIES with specific requirements
|
||||
□ Set real dates in TIMELINE AND MILESTONES
|
||||
□ Confirm BUDGET AND PAYMENT TERMS match agreement
|
||||
□ Add any additional clarifications needed
|
||||
□ Update legal entity name throughout contract
|
||||
□ Add specific milestone dates to calendar
|
||||
□ Create project folder with client-provided materials
|
||||
□ Document any verbal agreements in writing (email summary)
|
||||
□ Prepare final contract for client review
|
||||
□ Prepare invoice for initial payment (once contract signed)
|
||||
|
||||
|
||||
INTERVIEW NOTES TEMPLATE
|
||||
=========================
|
||||
|
||||
Use this template to organize notes during interview:
|
||||
|
||||
BUDGET & PAYMENT
|
||||
- Total budget acceptable: Y/N
|
||||
- Payment schedule preference: Upfront split / Monthly / Other: _______
|
||||
- Hosting billing preference: Annual / Monthly
|
||||
- ACF Pro license: Include / Client purchases
|
||||
- Ongoing costs acceptable: Y/N
|
||||
|
||||
MLS INTEGRATION
|
||||
- Subscribing to MLS: Y/N
|
||||
- Integration level: Manual / IDX Display / Full IDX / None
|
||||
- Property types: _______
|
||||
- MLS vs custom ratio: ___% MLS, ___% custom
|
||||
|
||||
PROPERTY FIELDS
|
||||
- Required fields: _______
|
||||
- Photos per listing: Min ___ Max ___ Avg ___
|
||||
- Search features needed: _______
|
||||
- Featured properties: Y/N
|
||||
- Show sold properties: Y/N
|
||||
|
||||
EMAIL
|
||||
- Current setup: _______
|
||||
- Number of accounts: ___
|
||||
- Migration option: Google Workspace / Forwarding / Keep current
|
||||
- Timing: _______
|
||||
|
||||
DESIGN
|
||||
- Logo available: Y/N (format: _______)
|
||||
- Brand colors: _______
|
||||
- Design direction: Custom / Template / Splash page adaptation
|
||||
- Inspiration sites: _______
|
||||
|
||||
CONTENT
|
||||
- Existing content: _______
|
||||
- Content creation: Client provides / Need help
|
||||
- Photos: Client provides / Need stock
|
||||
- Domain: _______
|
||||
|
||||
USERS & TRAINING
|
||||
- Team members: _______
|
||||
- Tech skill level (1-10): ___
|
||||
- Training preference: _______
|
||||
- Support expectations: _______
|
||||
|
||||
TIMELINE
|
||||
- Launch urgency: Urgent / Date: _____ / Flexible
|
||||
- Queue time acceptable: Y/N
|
||||
- Content ready by: _______
|
||||
|
||||
BUSINESS INFO
|
||||
- Legal name: _______
|
||||
- Signer name: _______ Title: _______
|
||||
- Contact email: _______
|
||||
- Payment method: _______
|
||||
- Business type: _______
|
||||
|
||||
TECHNICAL
|
||||
- Domain: _______
|
||||
- Email addresses needed: _______
|
||||
- Integrations: _______
|
||||
- Compliance needs: _______
|
||||
|
||||
FUTURE
|
||||
- Year 1 property volume: ___
|
||||
- Future features: _______
|
||||
- Success metrics: _______
|
||||
|
||||
NOTES & ACTION ITEMS
|
||||
_______________________________________________________
|
||||
_______________________________________________________
|
||||
_______________________________________________________
|
||||
@@ -0,0 +1,382 @@
|
||||
HOMEPROZ PROJECT - MEETING NOTES AND CONTRACT UPDATES
|
||||
======================================================
|
||||
Date: October 29, 2025
|
||||
|
||||
|
||||
MEETING SUMMARY (FROM AI TRANSCRIPT)
|
||||
====================================
|
||||
|
||||
Client: HomeProz (new housing division, separate from Landproz)
|
||||
Contact: Dayna Gottberg
|
||||
Status: Startup with limited operating funds
|
||||
|
||||
Key Discussion Points:
|
||||
----------------------
|
||||
|
||||
1. Website Needs
|
||||
- Already acquired domain (homeproz.com assumed)
|
||||
- Currently has basic GoDaddy splash page
|
||||
- Need proper website with backend for property listings
|
||||
- WordPress recommended with Advanced Custom Fields (ACF)
|
||||
- Estimated development time: ~40 hours (~1 week of focused work)
|
||||
|
||||
2. Hosting Discussion
|
||||
- Hanson.xyz to provide managed hosting
|
||||
- WordPress hosting significantly cheaper than Landproz hosting
|
||||
- Cost: $20/month for hosting + $30/month for management = $50/month total
|
||||
- Management includes: maintenance, backups, real person handling issues
|
||||
- Note: Meeting discussed monthly, contract proposes annual billing ($600/year)
|
||||
|
||||
3. Development Cost
|
||||
- Estimated: ~40 hours of work
|
||||
- Theme cost mentioned: approximately $6,000
|
||||
- Timeline: Brian is booked for next 3 weeks (Auction Cast, Kodex, Ascent)
|
||||
- Development would start after current commitments complete
|
||||
|
||||
4. MLS Integration Discussion
|
||||
- Question about IDX integration benefits and costs
|
||||
- Northstar MLS is provider for Minnesota and Western Wisconsin
|
||||
- Application fee: $100 (one-time)
|
||||
- Monthly subscription: $55/month
|
||||
- Potential approach: Website could pull listing by MLS number
|
||||
- Also accommodate custom listings not on MLS (commercial properties, etc.)
|
||||
- Full automated IDX integration not initially scoped (would be additional)
|
||||
|
||||
5. Email Migration
|
||||
- Support for moving emails to Gmail/Google Workspace mentioned
|
||||
- Included as IT support service in project scope
|
||||
|
||||
|
||||
CONTRACT UPDATES MADE
|
||||
======================
|
||||
|
||||
Based on meeting notes, the following updates were made to the draft contract:
|
||||
|
||||
1. PROJECT OVERVIEW
|
||||
- Added description of HomeProz as new housing division startup
|
||||
- Detailed ACF-based property listing system
|
||||
- Explained MLS integration approach (MLS number field + custom listings)
|
||||
- Updated timeline to reflect 1 week development + 3-4 week queue period
|
||||
|
||||
2. PROJECT DELIVERABLES
|
||||
- Expanded WordPress Development section with specific property fields
|
||||
- Added "Advanced Custom Fields (ACF) Implementation" section
|
||||
- Added "MLS Integration Planning" section
|
||||
- Added "Email Migration Support" section (up to 2 hours)
|
||||
- Updated hosting section to detail managed hosting setup
|
||||
- Specified ACF Pro plugin installation and configuration
|
||||
|
||||
3. EXCLUSIONS
|
||||
- Clarified that full IDX integration is excluded (planning included)
|
||||
- Added real estate-specific exclusions (mortgage calculators, virtual tours, etc.)
|
||||
- Noted ongoing MLS and Google Workspace fees are client responsibility
|
||||
- Maintained standard exclusions (e-commerce, CRM integration, etc.)
|
||||
|
||||
4. CLIENT RESPONSIBILITIES
|
||||
- Added specific content requirements (company info, property data)
|
||||
- Added requirement for MLS account registration (if desired)
|
||||
- Added requirement for Google Workspace registration (if desired)
|
||||
- Added GoDaddy access for DNS configuration
|
||||
|
||||
5. TIMELINE
|
||||
- Updated to show 3-4 week pre-development queue period
|
||||
- Detailed 1-week intensive development schedule
|
||||
- Added specific phases (planning, development, testing, launch)
|
||||
- Noted current project commitments causing delay
|
||||
|
||||
6. BUDGET AND PAYMENT TERMS
|
||||
- Changed from $7,000 to $6,000 (startup discount mentioned in meeting)
|
||||
- Effective rate: $150/hour vs standard $175/hour
|
||||
- Split payment: $2,000 upfront, $4,000 on completion
|
||||
- Added separate "Managed Hosting Service" section
|
||||
- Annual hosting: $600/year ($50/month equivalent)
|
||||
- Detailed what's included in managed hosting
|
||||
- Added "Additional Services" section for MLS and Google costs
|
||||
- Created "Total First Year Investment Summary" showing $6,600 total
|
||||
(Note: Meeting transcript said ~$6,000 for theme, contract now shows
|
||||
$6,000 development + $600 hosting = $6,600 first year total)
|
||||
|
||||
|
||||
PRICING ANALYSIS
|
||||
================
|
||||
|
||||
Meeting Discussion vs Contract:
|
||||
--------------------------------
|
||||
Meeting mentioned: ~$6,000 for "theme"
|
||||
Contract proposes:
|
||||
- $6,000 website development (one-time)
|
||||
- $600 hosting (annual, first year due at launch)
|
||||
- Total first year: $6,600
|
||||
|
||||
Hosting:
|
||||
--------
|
||||
Meeting discussed: $50/month ($20 hosting + $30 management)
|
||||
Contract proposes: $600/year (equivalent to $50/month, billed annually)
|
||||
|
||||
Rationale for annual billing:
|
||||
- Reduces administrative overhead (one invoice vs 12)
|
||||
- Standard practice for hosting services
|
||||
- Provides budget certainty for both parties
|
||||
- First year due at launch, renewals on anniversary
|
||||
|
||||
Note: Client may prefer monthly billing. This should be clarified in interview.
|
||||
|
||||
|
||||
SCOPE CLARIFICATIONS NEEDED
|
||||
============================
|
||||
|
||||
Items mentioned but needing more detail:
|
||||
|
||||
1. MLS Integration Scope
|
||||
- Is Northstar MLS subscription definitely happening?
|
||||
- Level of integration: just MLS number field, or automated import?
|
||||
- Contract includes planning and MLS field; excludes full IDX
|
||||
- May need to expand scope if automated IDX desired
|
||||
|
||||
2. Email Migration Details
|
||||
- How many email accounts need migration?
|
||||
- What's current email setup? (GoDaddy email? Other provider?)
|
||||
- Do they want Google Workspace or just Gmail forwarding?
|
||||
- 2 hours included may not be enough for complex migration
|
||||
|
||||
3. Existing Theme/Design
|
||||
- What is the "existing HomeProz design aesthetic"?
|
||||
- Is there a logo? Brand guidelines? Color scheme?
|
||||
- Is there a separate HomeProz brand from Landproz?
|
||||
- GoDaddy splash page - does it have design elements to reference?
|
||||
|
||||
4. Property Listing Requirements
|
||||
- What property types? (residential, commercial, land, all?)
|
||||
- What specific fields are needed beyond basics?
|
||||
- Photo gallery requirements (how many photos per listing?)
|
||||
- Map integration preferences (Google Maps, Mapbox, etc.?)
|
||||
|
||||
5. Advanced Features
|
||||
- Property search/filtering - how sophisticated?
|
||||
- Featured listings on homepage?
|
||||
- Property comparison tools?
|
||||
- Lead capture forms per property?
|
||||
- Social sharing for listings?
|
||||
|
||||
|
||||
ACF PRO LICENSING NOTE
|
||||
=======================
|
||||
|
||||
Advanced Custom Fields Pro is a premium WordPress plugin.
|
||||
|
||||
License cost: $49-249 depending on number of sites
|
||||
- Personal: $49/year (1 site) - likely choice for this project
|
||||
- Freelancer: $149/year (unlimited client sites)
|
||||
- Agency: $249/year (unlimited sites + advanced features)
|
||||
|
||||
Recommendation:
|
||||
- Include ACF Pro Personal license ($49/year) in development cost
|
||||
- Or client purchases license (their name, their renewal responsibility)
|
||||
- Needs to be clarified in contract or interview
|
||||
|
||||
Current contract states "Advanced Custom Fields Pro plugin" will be installed
|
||||
but doesn't specify who purchases license or renewal responsibility.
|
||||
|
||||
Add to contract:
|
||||
- ACF Pro license (1 year) included in development cost, or
|
||||
- Client responsible for ACF Pro license purchase and renewal
|
||||
|
||||
|
||||
QUESTIONS RAISED BY MEETING NOTES
|
||||
==================================
|
||||
|
||||
1. Budget Sensitivity
|
||||
Meeting noted "limited operating funds as a startup"
|
||||
- Is $6,600 first year within budget?
|
||||
- Would client prefer payment plan options?
|
||||
- Should we offer phase 1 (basic site) + phase 2 (MLS) approach?
|
||||
|
||||
2. Launch Urgency
|
||||
- How soon do they need to be live?
|
||||
- Are there business drivers for timeline?
|
||||
- Can they wait 3-4 weeks for development to start?
|
||||
|
||||
3. Landproz Relationship
|
||||
- HomeProz is "separate from Landproz" per meeting
|
||||
- But same contact person (Dayna Gottberg)
|
||||
- Shared resources? Shared branding? Completely independent?
|
||||
- Does Landproz success/relationship influence this project?
|
||||
|
||||
4. Property Volume
|
||||
- How many properties do they expect to list?
|
||||
- Starting inventory? Growth projections?
|
||||
- Impacts hosting resource allocation
|
||||
|
||||
5. Team Size
|
||||
- Who will be managing the website day-to-day?
|
||||
- How many people need training?
|
||||
- Technical skill level of users?
|
||||
|
||||
|
||||
RECOMMENDATIONS FOR INTERVIEW
|
||||
==============================
|
||||
|
||||
Priority 1 - Must Know Before Contract Finalized:
|
||||
--------------------------------------------------
|
||||
1. Confirm $6,600 first year total is within budget
|
||||
2. Clarify MLS integration scope (field only vs full IDX)
|
||||
3. Determine email migration complexity (account count, current setup)
|
||||
4. Review existing HomeProz branding/design materials
|
||||
5. Confirm hosting billing preference (annual vs monthly)
|
||||
|
||||
Priority 2 - Important for Accurate Scope:
|
||||
-------------------------------------------
|
||||
6. Define property listing field requirements specifically
|
||||
7. Understand property search/filtering needs
|
||||
8. Clarify ACF Pro license purchase/renewal responsibility
|
||||
9. Determine urgency and timeline flexibility
|
||||
10. Identify who will use the system (number of users, skill levels)
|
||||
|
||||
Priority 3 - Nice to Have for Planning:
|
||||
----------------------------------------
|
||||
11. Expected property volume and growth
|
||||
12. Future feature wishlist (to plan for extensibility)
|
||||
13. Relationship between HomeProz and Landproz brands
|
||||
14. Integration needs with other systems (if any)
|
||||
15. Success metrics (what makes this project successful?)
|
||||
|
||||
|
||||
RISK FACTORS IDENTIFIED
|
||||
========================
|
||||
|
||||
1. Limited Budget
|
||||
- Startup with "limited operating funds"
|
||||
- May have difficulty with upfront payment
|
||||
- May push for reduced scope or phased approach
|
||||
- Mitigation: Offer payment plan, phase approach, or scaled-back version
|
||||
|
||||
2. Scope Ambiguity
|
||||
- MLS integration mentioned but level unclear
|
||||
- Could expand significantly if expecting full IDX
|
||||
- Email migration could be complex
|
||||
- Mitigation: Very clear scope definition, IDX as separate phase/quote
|
||||
|
||||
3. Design Expectations
|
||||
- "Existing HomeProz design" referenced but may not exist yet
|
||||
- Startup may not have professional branding
|
||||
- May expect more design work than scoped
|
||||
- Mitigation: Clarify existing assets, set design scope limits
|
||||
|
||||
4. Timeline Pressure
|
||||
- Startups often need to launch quickly
|
||||
- 3-4 week delay may be problematic
|
||||
- Mitigation: Clear communication about queue, option to delay contract signing
|
||||
|
||||
5. Ongoing Costs
|
||||
- MLS: $660/year
|
||||
- Hosting: $600/year
|
||||
- Google Workspace: ~$72+/year
|
||||
- Total: ~$1,332+/year ongoing
|
||||
- For limited-budget startup, this may be concerning
|
||||
- Mitigation: Clear cost breakdown, discuss alternatives
|
||||
|
||||
|
||||
NEXT STEPS CHECKLIST
|
||||
=====================
|
||||
|
||||
Before sending contract to client:
|
||||
□ Conduct interview using prepared questions (see separate document)
|
||||
□ Review and verify all answers in contract
|
||||
□ Confirm pricing structure and budget fit
|
||||
□ Clarify MLS integration scope definitively
|
||||
□ Determine ACF Pro license responsibility
|
||||
□ Get copies of existing branding materials
|
||||
□ Verify contact information and legal entity name
|
||||
□ Set specific contract signing and start dates
|
||||
□ Confirm hosting billing preference (annual vs monthly)
|
||||
□ Review and adjust scope based on interview responses
|
||||
|
||||
After contract review:
|
||||
□ Be prepared to adjust scope if budget is tight
|
||||
□ Consider offering phased approach if needed
|
||||
□ Have alternative pricing options ready
|
||||
□ Document any verbal agreements in writing
|
||||
□ Set clear expectations about 3-4 week queue time
|
||||
|
||||
|
||||
COMPARISON TO LANDPROZ RELATIONSHIP
|
||||
====================================
|
||||
|
||||
This may influence approach:
|
||||
|
||||
Landproz Relationship:
|
||||
- Established client since 2022
|
||||
- Multiple large projects ($36k, $10.5k)
|
||||
- Ongoing hosting and maintenance
|
||||
- Trust and history established
|
||||
- Complex custom software (auction platform)
|
||||
|
||||
HomeProz Relationship:
|
||||
- New client (through Landproz connection)
|
||||
- Smaller initial project ($6k)
|
||||
- Startup with limited budget
|
||||
- Simpler website needs (property listings)
|
||||
- Opportunity for long-term relationship
|
||||
|
||||
Considerations:
|
||||
- HomeProz may expect "Landproz pricing" or treatment
|
||||
- Startup discount already applied ($150/hr vs $175/hr)
|
||||
- May lead to future work if successful
|
||||
- Good will with Dayna Gottberg benefits both relationships
|
||||
- But must maintain profitable pricing and clear scope
|
||||
|
||||
|
||||
STRATEGIC RECOMMENDATIONS
|
||||
==========================
|
||||
|
||||
1. Positioning
|
||||
- Position as "startup package" with room to grow
|
||||
- Emphasize value: real person support vs automated hosting
|
||||
- Highlight Landproz connection and proven track record
|
||||
- Make them feel like they're getting Landproz-quality at startup pricing
|
||||
|
||||
2. Phasing Option
|
||||
If budget is concern, offer phases:
|
||||
- Phase 1 ($4,000): Basic site + manual property listings
|
||||
- Phase 2 ($2,000): ACF system + advanced property management
|
||||
- Phase 3 (future): Full IDX MLS integration
|
||||
|
||||
3. Hosting Flexibility
|
||||
- Could offer first 3 months hosting free (include in dev cost)
|
||||
- Builds in trial period, reduces first-year cash outlay
|
||||
- Adjust contract: $6,000 dev + hosting starts month 4
|
||||
|
||||
4. Long-term Relationship
|
||||
- This is likely a long-term hosting client
|
||||
- Initial project may be break-even or low margin
|
||||
- Hosting and future enhancements are where relationship value is
|
||||
- Prioritize good experience over maximizing initial revenue
|
||||
|
||||
5. Referral Potential
|
||||
- Success here could lead to referrals in real estate space
|
||||
- Dayna Gottberg is well-connected in industry
|
||||
- Professional execution could generate significant future business
|
||||
|
||||
|
||||
CONTRACT DOCUMENT STATUS
|
||||
=========================
|
||||
|
||||
Documents Updated:
|
||||
✓ DRAFT-HomeProz-WordPress-Website-Contract.txt
|
||||
- All major sections updated with meeting information
|
||||
- Specific deliverables added
|
||||
- Pricing structure defined
|
||||
- Timeline clarified
|
||||
- Ready for final customization after interview
|
||||
|
||||
Still To Do:
|
||||
- Insert actual contract signing date
|
||||
- Update specific milestone dates based on calendar
|
||||
- Possibly adjust hosting billing (annual vs monthly)
|
||||
- Possibly adjust MLS integration scope
|
||||
- Possibly adjust ACF Pro license responsibility
|
||||
- Final proofread after interview responses incorporated
|
||||
|
||||
Next Document to Create:
|
||||
- Interview questions document (comprehensive question list)
|
||||
- Will help gather all information needed to finalize contract
|
||||
@@ -0,0 +1,272 @@
|
||||
HOMEPROZ CONTRACT - START HERE
|
||||
===============================
|
||||
Last Updated: October 29, 2025
|
||||
|
||||
|
||||
WHAT'S BEEN COMPLETED
|
||||
=====================
|
||||
|
||||
✓ Draft contract created based on Landproz templates
|
||||
✓ Meeting notes analyzed and incorporated
|
||||
✓ Scope defined: WordPress + ACF property listing system
|
||||
✓ Pricing locked: $6,000 development + $600 hosting = $6,600 first year
|
||||
✓ Your decisions incorporated:
|
||||
- ACF Pro license managed by you (included in hosting)
|
||||
- Annual billing only ($600/year)
|
||||
- 3-4 week timeline firm, non-negotiable
|
||||
- $6,000 is hard number
|
||||
- MLS manual entry only
|
||||
- Email migration 2 hours, no special considerations
|
||||
|
||||
|
||||
THE CONTRACT IS 95% DONE
|
||||
=========================
|
||||
|
||||
File: DRAFT-HomeProz-WordPress-Website-Contract.txt
|
||||
|
||||
What's complete:
|
||||
- Full project scope and deliverables
|
||||
- Complete legal terms section
|
||||
- Payment structure and terms
|
||||
- Timeline and milestones
|
||||
- Exclusions clearly defined
|
||||
- All your decisions locked in
|
||||
|
||||
What's still needed:
|
||||
1. Client legal business name (confirm with Dayna)
|
||||
2. Insert actual dates or make relative to signing
|
||||
3. Format to Word document
|
||||
4. Final proofread
|
||||
|
||||
|
||||
YOUR NEXT 3 STEPS
|
||||
==================
|
||||
|
||||
STEP 1: Get Client Info (5 minutes)
|
||||
------------------------------------
|
||||
Email Dayna:
|
||||
"Hi Dayna - Putting together the HomeProz website contract. Need to confirm:
|
||||
1. Legal business name? (HomeProz LLC? Inc.? Other?)
|
||||
2. Who signs? (Name and title)
|
||||
3. Email for invoices?
|
||||
4. Do you have HomeProz logo in digital format?
|
||||
Thanks, Brian"
|
||||
|
||||
|
||||
STEP 2: Finalize Contract (30 minutes)
|
||||
---------------------------------------
|
||||
When you get response:
|
||||
1. Update contract with legal business name
|
||||
2. Insert dates (or make relative: "3-4 weeks after signing")
|
||||
3. Convert text file to Word document
|
||||
4. Format professionally (headings, spacing, signature blocks)
|
||||
5. Final proofread
|
||||
|
||||
|
||||
STEP 3: Send to Client (5 minutes)
|
||||
-----------------------------------
|
||||
Email contract with brief message:
|
||||
- Project summary
|
||||
- Total: $6,600 first year
|
||||
- Timeline: 4-5 weeks
|
||||
- Ask them to review and reply with questions
|
||||
- Set review deadline (5-7 business days)
|
||||
|
||||
|
||||
SIMPLIFIED CONTRACT SUMMARY
|
||||
============================
|
||||
|
||||
WHAT: WordPress website with property listing system using ACF
|
||||
WHO: HomeProz (startup real estate division)
|
||||
WHEN: 4-5 weeks from signing (3-4 week queue + 1 week development)
|
||||
HOW MUCH:
|
||||
- Development: $6,000 ($2k upfront, $4k on completion)
|
||||
- Hosting: $600/year (annual billing only)
|
||||
- Total Year 1: $6,600
|
||||
|
||||
WHAT'S INCLUDED:
|
||||
- Custom WordPress theme based on HomeProz brand
|
||||
- ACF Pro for property listings (license managed by you)
|
||||
- Property search and filtering
|
||||
- MLS number field (manual entry only)
|
||||
- Email migration (2 hours)
|
||||
- Managed hosting with security, backups, updates
|
||||
- Training and documentation
|
||||
- 60-day warranty
|
||||
|
||||
WHAT'S EXCLUDED:
|
||||
- Automated IDX integration (future project)
|
||||
- Content writing/photography
|
||||
- Logo/branding design
|
||||
- E-commerce
|
||||
|
||||
|
||||
KEY DOCUMENTS IN THIS FOLDER
|
||||
=============================
|
||||
|
||||
READ THESE IN ORDER:
|
||||
|
||||
1. README-START-HERE.txt (this file)
|
||||
Quick overview and next steps
|
||||
|
||||
2. CONTRACT-AT-A-GLANCE.txt
|
||||
Quick reference summary of contract terms
|
||||
|
||||
3. DRAFT-HomeProz-WordPress-Website-Contract.txt
|
||||
THE ACTUAL CONTRACT - this is what you'll format and send
|
||||
|
||||
4. FINAL-DECISIONS-AND-REMAINING-TASKS.txt
|
||||
Detailed checklist of what's done and what's left
|
||||
|
||||
5. INTERVIEW-QUESTIONS-FOR-CLIENT.txt
|
||||
Comprehensive questions (may not need since you know client)
|
||||
|
||||
6. MEETING-NOTES-AND-UPDATES.txt
|
||||
Analysis of meeting transcript and strategic recommendations
|
||||
|
||||
OPTIONAL REFERENCE:
|
||||
7. SUMMARY-AND-NEXT-STEPS.txt
|
||||
8. CONTRACT-KEY-ELEMENTS-EXTRACTED.txt
|
||||
9. FEEDBACK-QUESTIONS-RECOMMENDATIONS.txt
|
||||
10. reference_examples/ folder - Landproz contracts
|
||||
|
||||
|
||||
ANTICIPATED TIMELINE FROM NOW
|
||||
==============================
|
||||
|
||||
Today (Oct 29):
|
||||
- Email Dayna for client info
|
||||
|
||||
Tomorrow-ish:
|
||||
- Receive response from Dayna
|
||||
- Finalize contract
|
||||
- Format to Word
|
||||
- Send to client
|
||||
|
||||
5-7 days later:
|
||||
- Client reviews and signs
|
||||
- Client sends $2,000 payment
|
||||
|
||||
3-4 weeks after signing:
|
||||
- Complete current projects
|
||||
- Start HomeProz development
|
||||
|
||||
1 week of development:
|
||||
- Build site
|
||||
- Client review
|
||||
- Revisions
|
||||
|
||||
~4-5 weeks after signing:
|
||||
- Launch
|
||||
- Training
|
||||
- Collect final payment ($4,600)
|
||||
|
||||
Ongoing:
|
||||
- Annual hosting ($600/year)
|
||||
- Potential future enhancements
|
||||
|
||||
|
||||
COMMON QUESTIONS & YOUR ANSWERS
|
||||
================================
|
||||
|
||||
Q: "Can you start sooner?"
|
||||
A: "No - 3-4 week queue is firm due to current commitments."
|
||||
|
||||
Q: "Can we do monthly billing?"
|
||||
A: "No - annual billing only for administrative efficiency."
|
||||
|
||||
Q: "Can we reduce the price?"
|
||||
A: "$6,000 is already discounted from $7,000. Price is firm."
|
||||
|
||||
Q: "What about phased approach?"
|
||||
A: "No - project is complete deliverable at $6,000."
|
||||
|
||||
Q: "Can we add full IDX integration?"
|
||||
A: "Not in this project - that's a separate future project if desired."
|
||||
|
||||
Q: "What if email migration takes longer?"
|
||||
A: "Additional time billed at $175/hour, but I expect 2 hours will be enough."
|
||||
|
||||
|
||||
IF CLIENT PUSHES BACK ON ANYTHING
|
||||
==================================
|
||||
|
||||
Budget too high:
|
||||
- Remind them this is already discounted ($150/hr vs $175/hr standard)
|
||||
- Explain value: custom property system, managed hosting, ongoing support
|
||||
- If they truly can't afford it, this may not be the right project to take on
|
||||
|
||||
Timeline too long:
|
||||
- Be honest: you have commitments that must be completed first
|
||||
- Explain that 3-4 weeks lets them prepare content and materials
|
||||
- Emphasize quality over speed
|
||||
|
||||
Wants monthly hosting:
|
||||
- Explain administrative burden of 12 invoices vs 1
|
||||
- Total cost is identical
|
||||
- This is your standard practice
|
||||
|
||||
Any scope additions:
|
||||
- Use change order process: written approval, quote at $250/hour
|
||||
- Or defer to Phase 2 after launch
|
||||
- Protect the $6,000 fixed fee
|
||||
|
||||
|
||||
YOUR POSITION
|
||||
=============
|
||||
|
||||
You have:
|
||||
- Professional contract based on proven templates
|
||||
- Fair pricing (discounted for startup)
|
||||
- Clear scope with proper boundaries
|
||||
- Realistic timeline
|
||||
- All standard legal protections
|
||||
|
||||
You should:
|
||||
- Be confident in the proposal
|
||||
- Be firm on price, timeline, and scope
|
||||
- Be helpful and professional
|
||||
- Be willing to walk away if not right fit
|
||||
|
||||
This is a good project if:
|
||||
- They accept terms as presented
|
||||
- They have realistic expectations
|
||||
- They can provide materials promptly
|
||||
- Long-term hosting relationship is likely
|
||||
|
||||
This is NOT a good project if:
|
||||
- They want major discounts or scope expansion
|
||||
- They can't accept timeline
|
||||
- They seem difficult or demanding
|
||||
- Risk outweighs reward
|
||||
|
||||
|
||||
REMEMBER
|
||||
========
|
||||
|
||||
- This is a relationship business (Dayna connects you to Landproz too)
|
||||
- Good execution could lead to referrals
|
||||
- Hosting is where long-term value is ($600/year recurring)
|
||||
- Professional boundaries protect both parties
|
||||
- Clear scope prevents future problems
|
||||
- Written agreement is essential
|
||||
|
||||
|
||||
LITERALLY JUST DO THIS
|
||||
=======================
|
||||
|
||||
1. Email Dayna asking for legal business name and signing info
|
||||
2. Wait for response
|
||||
3. Update contract with her info
|
||||
4. Format to Word
|
||||
5. Send to Dayna
|
||||
6. Answer any questions
|
||||
7. Get signed contract and $2,000 payment
|
||||
8. Build website in 4-5 weeks
|
||||
9. Collect final payment
|
||||
10. Manage hosting ongoing
|
||||
|
||||
That's it. You're ready.
|
||||
|
||||
|
||||
CONTRACT STATUS: 95% COMPLETE - JUST NEEDS CLIENT INFO AND FORMATTING
|
||||
@@ -0,0 +1,489 @@
|
||||
HOMEPROZ CONTRACT - SUMMARY AND NEXT STEPS
|
||||
===========================================
|
||||
Date: October 29, 2025
|
||||
|
||||
|
||||
WHAT HAS BEEN COMPLETED
|
||||
========================
|
||||
|
||||
1. DRAFT CONTRACT CREATED
|
||||
File: DRAFT-HomeProz-WordPress-Website-Contract.txt
|
||||
|
||||
Status: Substantially complete, ready for final customization after interview
|
||||
|
||||
Key sections populated based on meeting notes:
|
||||
✓ Project overview with ACF property listing system description
|
||||
✓ Detailed deliverables including WordPress development, ACF implementation,
|
||||
MLS planning, email migration support, managed hosting setup
|
||||
✓ Clear exclusions (full IDX integration, e-commerce, etc.)
|
||||
✓ Client responsibilities specific to real estate website
|
||||
✓ Timeline showing 3-4 week queue + 1 week development
|
||||
✓ Budget: $6,000 development + $600 annual hosting = $6,600 first year
|
||||
✓ Payment schedule: $2,000 upfront, $4,000 on completion
|
||||
✓ Complete legal terms section (all standard clauses from Landproz contracts)
|
||||
|
||||
Still needs:
|
||||
- Actual contract signing date
|
||||
- Specific milestone calendar dates
|
||||
- Possible adjustments based on interview responses
|
||||
- Client's legal business entity name confirmation
|
||||
- Final proofread
|
||||
|
||||
2. SUPPORTING DOCUMENTS CREATED
|
||||
|
||||
CONTRACT-KEY-ELEMENTS-EXTRACTED.txt
|
||||
- Reference guide of all elements extracted from Landproz contracts
|
||||
- Legal clauses, payment structures, standard terms
|
||||
- Useful for understanding contract construction
|
||||
|
||||
MEETING-NOTES-AND-UPDATES.txt
|
||||
- Detailed summary of meeting transcript information
|
||||
- Analysis of what was discussed vs what's in contract
|
||||
- Risk factors, strategic recommendations
|
||||
- Comparison to Landproz relationship
|
||||
|
||||
INTERVIEW-QUESTIONS-FOR-CLIENT.txt
|
||||
- Comprehensive question list organized by topic
|
||||
- 12 sections covering all aspects of project
|
||||
- Post-interview checklist
|
||||
- Notes template for organizing responses
|
||||
|
||||
FEEDBACK-QUESTIONS-RECOMMENDATIONS.txt (original)
|
||||
- Initial feedback on draft before meeting notes
|
||||
- Still relevant for understanding contract structure
|
||||
|
||||
reference_examples/ directory
|
||||
- 6 Landproz contracts in text format
|
||||
- README explaining each document
|
||||
|
||||
|
||||
CURRENT CONTRACT HIGHLIGHTS
|
||||
============================
|
||||
|
||||
SCOPE:
|
||||
- WordPress website with Advanced Custom Fields for property listings
|
||||
- Theme based on existing HomeProz design
|
||||
- Property search and filtering
|
||||
- MLS number field (manual entry, not full automated IDX)
|
||||
- Email migration support (up to 2 hours)
|
||||
- Managed hosting setup
|
||||
- Training and documentation
|
||||
- 60-day warranty
|
||||
|
||||
PRICING:
|
||||
- Development: $6,000 (one-time)
|
||||
- Discounted from standard $7,000 (40 hrs × $175/hr)
|
||||
- Effective rate: $150/hr for startup client
|
||||
- Payment: $2,000 upfront, $4,000 on completion
|
||||
|
||||
- Hosting: $600/year (ongoing)
|
||||
- Equivalent to $50/month
|
||||
- Includes management, backups, security, updates, support
|
||||
- Billed annually (can change to monthly if client prefers)
|
||||
- First year due at launch
|
||||
|
||||
- Total First Year: $6,600
|
||||
|
||||
TIMELINE:
|
||||
- Contract signing → 3-4 weeks → Development starts
|
||||
- Development: ~1 week of focused work
|
||||
- Total: ~4-5 weeks from contract signing to launch
|
||||
|
||||
EXCLUSIONS:
|
||||
- Full automated IDX MLS integration
|
||||
- E-commerce/payments
|
||||
- Custom plugins beyond standard
|
||||
- Ongoing MLS fees ($660/year - client pays directly)
|
||||
- Ongoing Google Workspace fees (client pays directly)
|
||||
- Content writing/photography
|
||||
|
||||
|
||||
CRITICAL QUESTIONS TO ANSWER
|
||||
=============================
|
||||
|
||||
Before finalizing contract, you MUST determine:
|
||||
|
||||
1. BUDGET ACCEPTANCE
|
||||
Is $6,600 first year total within their budget?
|
||||
Can they do $2,000 upfront payment?
|
||||
Are ongoing costs ($600-2,000/year) acceptable?
|
||||
|
||||
2. MLS INTEGRATION SCOPE
|
||||
Are they subscribing to Northstar MLS?
|
||||
Do they want manual MLS field (included) or automated IDX (additional cost)?
|
||||
Current contract assumes manual field only.
|
||||
|
||||
3. EMAIL MIGRATION COMPLEXITY
|
||||
How many email accounts?
|
||||
Current setup?
|
||||
2 hours included - is this enough?
|
||||
|
||||
4. DESIGN/BRANDING ASSETS
|
||||
Do they actually have a "HomeProz design aesthetic"?
|
||||
Logo, colors, brand guidelines available?
|
||||
Or do they need design work beyond scope?
|
||||
|
||||
5. HOSTING BILLING PREFERENCE
|
||||
Annual ($600/year) or monthly ($50/month)?
|
||||
Contract currently shows annual.
|
||||
|
||||
6. ACF PRO LICENSE
|
||||
Include in your cost or client purchases separately?
|
||||
$49/year - needs to be assigned to someone.
|
||||
|
||||
7. LEGAL BUSINESS NAME
|
||||
Exact legal entity name for contract?
|
||||
"HomeProz" or "HomeProz LLC" or other?
|
||||
|
||||
8. TIMELINE ACCEPTABILITY
|
||||
Can they wait 3-4 weeks for development to start?
|
||||
Is there urgency requiring rush/prioritization?
|
||||
|
||||
|
||||
RECOMMENDED NEXT STEPS
|
||||
=======================
|
||||
|
||||
STEP 1: CONDUCT INTERVIEW
|
||||
--------------------------
|
||||
Use: INTERVIEW-QUESTIONS-FOR-CLIENT.txt
|
||||
|
||||
Method options:
|
||||
□ Schedule call/video meeting with Dayna
|
||||
□ Send questions via email (less ideal, conversation is better)
|
||||
□ Mix: Send key questions, then discuss responses
|
||||
|
||||
Key sections to cover:
|
||||
- Budget and payment (Q1.1-1.4)
|
||||
- MLS integration scope (Q2.1-2.5)
|
||||
- Email migration (Q4.1-4.3)
|
||||
- Design and branding (Q5.1-5.4)
|
||||
- Business and legal (Q9.1-9.4)
|
||||
|
||||
Don't need to ask every question - use judgment based on conversation flow.
|
||||
|
||||
STEP 2: UPDATE CONTRACT
|
||||
-----------------------
|
||||
After interview, update contract with:
|
||||
□ Insert contract signing date
|
||||
□ Calculate and insert specific milestone dates
|
||||
□ Adjust hosting billing if needed (annual vs monthly)
|
||||
□ Adjust MLS scope if needed (manual vs IDX)
|
||||
□ Clarify ACF Pro license responsibility
|
||||
□ Insert correct legal business entity name
|
||||
□ Adjust deliverables if scope changes based on interview
|
||||
□ Add any additional clarifications needed
|
||||
|
||||
STEP 3: INTERNAL REVIEW
|
||||
------------------------
|
||||
Before sending to client:
|
||||
□ Read contract as if you're the client
|
||||
□ Verify all [INSERT DATE] placeholders are filled
|
||||
□ Verify pricing math is correct
|
||||
□ Verify timeline is realistic and calendar dates work
|
||||
□ Check that scope matches what was discussed
|
||||
□ Proofread for typos and consistency
|
||||
□ Verify exclusions don't exclude something you plan to do
|
||||
|
||||
STEP 4: CLIENT REVIEW
|
||||
----------------------
|
||||
Send to client:
|
||||
□ Email the contract as Word document (format from text version)
|
||||
□ Include cover letter/email explaining:
|
||||
- Summary of project
|
||||
- Total investment ($6,600 first year)
|
||||
- Timeline (4-5 weeks from signing)
|
||||
- Next steps (review, sign, initial payment)
|
||||
□ Request review within 5-7 business days
|
||||
□ Offer to discuss any questions
|
||||
|
||||
STEP 5: NEGOTIATE/REVISE
|
||||
-------------------------
|
||||
Expect client may:
|
||||
- Request scope changes
|
||||
- Negotiate pricing
|
||||
- Request different payment terms
|
||||
- Have questions about technical details
|
||||
|
||||
Be prepared to:
|
||||
□ Adjust scope up or down
|
||||
□ Offer phased approach if budget tight
|
||||
□ Modify payment schedule if needed
|
||||
□ Clarify technical specifications
|
||||
□ Document all changes in writing
|
||||
|
||||
STEP 6: EXECUTE CONTRACT
|
||||
-------------------------
|
||||
Once agreed:
|
||||
□ Both parties sign (DocuSign or PDF signatures)
|
||||
□ Send invoice for initial $2,000 payment
|
||||
□ Set up project folder and files
|
||||
□ Add project to calendar with milestone dates
|
||||
□ Send welcome/kickoff email outlining next steps
|
||||
|
||||
STEP 7: PROJECT KICKOFF
|
||||
------------------------
|
||||
After payment received:
|
||||
□ Send confirmation and queue position update
|
||||
□ Request client provide materials (logo, content, access)
|
||||
□ Set up staging environment
|
||||
□ Schedule kickoff meeting for when development starts
|
||||
□ Keep client updated on queue status
|
||||
|
||||
|
||||
STRATEGIC CONSIDERATIONS
|
||||
=========================
|
||||
|
||||
BUDGET SENSITIVITY
|
||||
------------------
|
||||
Meeting notes indicated "limited operating funds as a startup"
|
||||
|
||||
If budget is tight:
|
||||
- Offer phased approach:
|
||||
- Phase 1 ($4,000): Basic site with manual property entry
|
||||
- Phase 2 ($2,000): ACF system upgrade
|
||||
- Phase 3 (future): Full IDX integration
|
||||
|
||||
- Or offer payment plan:
|
||||
- $500/month for 12 months = $6,000
|
||||
- Plus hosting $50/month
|
||||
- Total: $550/month for first year
|
||||
|
||||
- Or include first 3 months hosting free:
|
||||
- Development: $6,000 (includes 3 months hosting)
|
||||
- Hosting starts month 4
|
||||
- Reduces Year 1 cash outlay to $6,150
|
||||
|
||||
RELATIONSHIP VALUE
|
||||
------------------
|
||||
This is likely a long-term relationship:
|
||||
- Ongoing hosting: $600/year recurring revenue
|
||||
- Future enhancements: property of opportunities
|
||||
- Referral potential: Dayna is connected in real estate
|
||||
- Landproz connection: Good will benefits both relationships
|
||||
|
||||
Consider:
|
||||
- Initial project may be lower margin (startup discount)
|
||||
- Long-term value is in hosting and future work
|
||||
- Prioritize good experience over maximizing initial revenue
|
||||
- Professional execution could lead to significant referrals
|
||||
|
||||
SCOPE MANAGEMENT
|
||||
----------------
|
||||
Watch for scope creep in these areas:
|
||||
- MLS integration complexity (stay with manual unless explicitly scoped for IDX)
|
||||
- Email migration time (2 hours may not be enough for complex setups)
|
||||
- Design work (if they don't have brand assets, could expand significantly)
|
||||
- Custom feature requests during development
|
||||
- Training time if users are not technical
|
||||
|
||||
Mitigation:
|
||||
- Very clear scope definition before starting
|
||||
- Written change order process
|
||||
- Regular check-ins during development
|
||||
- Set expectations early about what's included vs additional
|
||||
|
||||
TECHNICAL NOTES
|
||||
---------------
|
||||
Items to verify/prepare before development:
|
||||
- ACF Pro license: Purchase or have client purchase before starting
|
||||
- Hosting server: Ensure resources allocated for new site
|
||||
- MLS research: If doing any MLS integration, research API/requirements
|
||||
- Google Workspace: Have signup process documented if assisting with email
|
||||
- Domain access: Get GoDaddy credentials early
|
||||
|
||||
|
||||
POTENTIAL ISSUES AND SOLUTIONS
|
||||
===============================
|
||||
|
||||
ISSUE: Timeline too long (3-4 week wait)
|
||||
SOLUTION OPTIONS:
|
||||
- Pay 20% rush fee ($1,200) for immediate start
|
||||
- Reduce scope to launch faster (basic site now, features later)
|
||||
- Accept timeline or wait until schedule opens
|
||||
|
||||
ISSUE: Budget too high
|
||||
SOLUTION OPTIONS:
|
||||
- Phased approach (launch basic site, add features later)
|
||||
- Payment plan spread over 12 months
|
||||
- Reduce scope (fewer features, simpler design)
|
||||
- Delay project until funding available
|
||||
|
||||
ISSUE: MLS integration expectations exceed manual entry
|
||||
SOLUTION OPTIONS:
|
||||
- Provide separate quote for full IDX integration
|
||||
- Recommend starting manual, adding IDX later
|
||||
- Research and quote IDX service fees clearly
|
||||
|
||||
ISSUE: Email migration more complex than 2 hours
|
||||
SOLUTION OPTIONS:
|
||||
- Provide quote for additional migration time at $175/hr
|
||||
- Client can handle migration themselves with documentation
|
||||
- Use migration service (additional cost)
|
||||
|
||||
ISSUE: No existing design/branding materials
|
||||
SOLUTION OPTIONS:
|
||||
- Add design phase to project (+$1,000-2,000)
|
||||
- Use template design with minimal customization
|
||||
- Refer to designer for branding, then proceed with web development
|
||||
|
||||
ISSUE: Client wants features not in scope
|
||||
SOLUTION OPTIONS:
|
||||
- Add via change order at $250/hr
|
||||
- Defer to Phase 2 after launch
|
||||
- Reduce other features to make room in budget
|
||||
|
||||
|
||||
ALTERNATIVES TO CONSIDER OFFERING
|
||||
==================================
|
||||
|
||||
ALTERNATIVE 1: PHASED APPROACH
|
||||
Phase 1 - Basic Site ($4,000)
|
||||
- WordPress installation
|
||||
- Basic theme setup
|
||||
- 3-5 standard pages
|
||||
- Contact form
|
||||
- Managed hosting setup
|
||||
- Manual property entry (standard posts/pages)
|
||||
|
||||
Phase 2 - Property System ($2,000)
|
||||
- Advanced Custom Fields implementation
|
||||
- Custom property listing system
|
||||
- Search and filtering
|
||||
- MLS number field
|
||||
|
||||
Phase 3 - Future Enhancements (quoted separately)
|
||||
- Full IDX integration
|
||||
- Advanced features
|
||||
- Marketing tools
|
||||
|
||||
ALTERNATIVE 2: TEMPLATE-BASED APPROACH ($3,500)
|
||||
- Premium real estate WordPress theme ($60)
|
||||
- Basic customization to HomeProz brand
|
||||
- Property listing setup using theme features
|
||||
- Managed hosting
|
||||
- Training
|
||||
|
||||
Faster/cheaper but less custom, may have limitations.
|
||||
|
||||
ALTERNATIVE 3: MONTHLY MANAGED SERVICE ($550/month)
|
||||
Year 1 (12 months):
|
||||
- Website development spread over payments
|
||||
- Managed hosting included
|
||||
- Ongoing support and updates
|
||||
|
||||
This cashflow-friendly option may appeal to startup.
|
||||
|
||||
|
||||
DECISION POINTS
|
||||
===============
|
||||
|
||||
YOU NEED TO DECIDE:
|
||||
|
||||
1. Are you firm on 3-4 week timeline or willing to prioritize for rush fee?
|
||||
2. Are you willing to do phased approach if full budget is issue?
|
||||
3. Minimum project size you'll accept if they want to reduce scope?
|
||||
4. ACF Pro license - include and manage or require client purchase?
|
||||
5. Hosting billing - prefer annual or okay with monthly?
|
||||
6. Email migration - strict 2 hour limit or flexible if needed?
|
||||
7. Design work - how much is included before additional charges?
|
||||
|
||||
|
||||
FILES SUMMARY
|
||||
=============
|
||||
|
||||
Working Directory: Clients/HomeProz/Contracts/WordPress-Website/
|
||||
|
||||
KEY FILES:
|
||||
1. DRAFT-HomeProz-WordPress-Website-Contract.txt
|
||||
→ Main contract document, ready for final customization
|
||||
|
||||
2. INTERVIEW-QUESTIONS-FOR-CLIENT.txt
|
||||
→ Use this for client interview to gather remaining information
|
||||
|
||||
3. SUMMARY-AND-NEXT-STEPS.txt (this file)
|
||||
→ Overview and action plan
|
||||
|
||||
REFERENCE FILES:
|
||||
4. MEETING-NOTES-AND-UPDATES.txt
|
||||
→ Detailed meeting analysis and strategic recommendations
|
||||
|
||||
5. CONTRACT-KEY-ELEMENTS-EXTRACTED.txt
|
||||
→ Contract building blocks from Landproz templates
|
||||
|
||||
6. FEEDBACK-QUESTIONS-RECOMMENDATIONS.txt
|
||||
→ Original feedback (before meeting notes)
|
||||
|
||||
7. reference_examples/ (directory)
|
||||
→ 6 Landproz contracts in text format
|
||||
|
||||
|
||||
IMMEDIATE ACTION REQUIRED
|
||||
==========================
|
||||
|
||||
Choose next step:
|
||||
|
||||
□ OPTION A: Interview client now
|
||||
- Review INTERVIEW-QUESTIONS-FOR-CLIENT.txt
|
||||
- Schedule call/meeting with Dayna
|
||||
- Gather all information
|
||||
- Update contract based on responses
|
||||
|
||||
□ OPTION B: Review contract first
|
||||
- Read through DRAFT-HomeProz-WordPress-Website-Contract.txt
|
||||
- Make any adjustments needed
|
||||
- Prepare questions or changes
|
||||
- Then proceed to interview
|
||||
|
||||
□ OPTION C: Send preliminary contract for review
|
||||
- Format draft into Word document
|
||||
- Send with note that it's preliminary, subject to discussion
|
||||
- Let client review and come back with questions
|
||||
- Finalize based on their feedback
|
||||
|
||||
RECOMMENDED: Option A (interview first)
|
||||
- Ensures contract is accurate before client sees it
|
||||
- Avoids back-and-forth revisions
|
||||
- Shows professionalism and thoroughness
|
||||
- Surfaces issues early
|
||||
|
||||
|
||||
FINAL NOTES
|
||||
===========
|
||||
|
||||
Contract Quality:
|
||||
The draft contract is professional, comprehensive, and based on proven templates
|
||||
from successful Landproz projects. All essential legal protections are in place.
|
||||
With minor customization after interview, it will be ready to send.
|
||||
|
||||
Scope Accuracy:
|
||||
The current scope reflects meeting discussion but needs validation:
|
||||
- Is manual MLS field entry really what they want?
|
||||
- Is 2 hours enough for email migration?
|
||||
- Do they actually have design materials or need design work?
|
||||
- Is $6,600 truly within startup budget?
|
||||
|
||||
Interview will answer these questions definitively.
|
||||
|
||||
Timeline Reality:
|
||||
The 3-4 week queue is honest and sets proper expectations. If this is
|
||||
problematic for client, better to know now and offer alternatives (rush fee,
|
||||
phased approach, etc.) than to over-promise and under-deliver.
|
||||
|
||||
Relationship Approach:
|
||||
This is a relationship business. Dayna Gottberg is the connection to both
|
||||
HomeProz and Landproz. Professional execution on this project could lead to:
|
||||
- Long-term hosting relationship ($600/year recurring)
|
||||
- Future development work
|
||||
- Referrals in real estate industry
|
||||
- Strengthened relationship with Landproz
|
||||
|
||||
Prioritize good experience and fair pricing over maximizing immediate revenue.
|
||||
|
||||
Ready to Proceed:
|
||||
You have everything needed to move forward:
|
||||
✓ Professional contract draft
|
||||
✓ Comprehensive interview questions
|
||||
✓ Strategic analysis and recommendations
|
||||
✓ Reference materials from past successful projects
|
||||
|
||||
Next step: Conduct interview and finalize contract details.
|
||||
@@ -0,0 +1,807 @@
|
||||
# HomeProz WordPress Website Design Document
|
||||
## Draft v1.0 - For Review
|
||||
|
||||
---
|
||||
|
||||
## 1. Executive Summary
|
||||
|
||||
This document outlines the recommended design approach for the new HomeProz WordPress website. The design will maintain the client's established brand identity while modernizing the presentation and improving user experience through better organization, clearer hierarchy, and enhanced property listing functionality.
|
||||
|
||||
---
|
||||
|
||||
## 2. Current Site Analysis
|
||||
|
||||
### 2.1 Existing Site Overview
|
||||
- **Platform**: GoDaddy Website Builder 8.0
|
||||
- **URL**: https://homeprozrealestate.com/
|
||||
- **Structure**: Single-page scrolling site with sections
|
||||
|
||||
### 2.2 Current Sections (in order)
|
||||
1. Header with logo and hamburger menu
|
||||
2. Hero section - "Find Your Dream Home Today"
|
||||
3. Current Listings carousel (circular images)
|
||||
4. Our Mission statement
|
||||
5. Meet Our Agents (team profiles)
|
||||
6. Testimonials
|
||||
7. Contact form
|
||||
8. Office location & phone numbers
|
||||
9. Social media links (Facebook, TikTok)
|
||||
10. Photo gallery
|
||||
11. Footer with legal/copyright
|
||||
|
||||
### 2.3 Current Brand Elements
|
||||
|
||||
#### Color Palette
|
||||
| Color | Hex Code | Usage |
|
||||
|-------|----------|-------|
|
||||
| Primary Dark | `#000000` | Background |
|
||||
| Accent Red/Rust | `#9F3730` | Buttons, accents |
|
||||
| Accent Light | `#BF524B` | Links |
|
||||
| Hover State | `#EA9491` | Link hover |
|
||||
| Text Light | `#E2E2E2` | Body text |
|
||||
| White | `#FFFFFF` | Headings, highlights |
|
||||
|
||||
#### Typography
|
||||
| Element | Font | Weight |
|
||||
|---------|------|--------|
|
||||
| Headlines | Abril Fatface | 400 |
|
||||
| Body Text | Droid Sans | 400, 700 |
|
||||
|
||||
### 2.4 Current Strengths
|
||||
- Clean, minimalist dark aesthetic
|
||||
- Clear brand colors (rust/terracotta accent)
|
||||
- Professional team photos
|
||||
- Mobile responsive
|
||||
- Contact information prominent
|
||||
|
||||
### 2.5 Current Weaknesses
|
||||
- Property listings link to external sites (Zillow, HomeFinder)
|
||||
- No internal property detail pages
|
||||
- Limited search/filter functionality
|
||||
- Circular crop on property images loses context
|
||||
- No MLS integration or property management
|
||||
- Cookie consent popup needs styling improvement
|
||||
- Footer is cluttered with legal text
|
||||
- Limited SEO capabilities
|
||||
|
||||
---
|
||||
|
||||
## 3. Recommended Design Direction
|
||||
|
||||
### 3.1 Design Philosophy
|
||||
**"Modern Minimalist Real Estate"** - Retain the sophisticated dark theme while adding:
|
||||
- Better visual hierarchy
|
||||
- Improved property presentation
|
||||
- Professional real estate conventions
|
||||
- Enhanced usability
|
||||
|
||||
### 3.2 Refined Color Palette
|
||||
|
||||
| Color | Hex Code | CSS Variable | Usage |
|
||||
|-------|----------|--------------|-------|
|
||||
| Background Dark | `#0A0A0A` | `--color-bg-dark` | Primary background (slightly softer than pure black) |
|
||||
| Background Card | `#161616` | `--color-bg-card` | Card backgrounds, elevated surfaces |
|
||||
| Accent Primary | `#9F3730` | `--color-accent` | CTAs, buttons, highlights |
|
||||
| Accent Hover | `#C8473F` | `--color-accent-hover` | Button hover states |
|
||||
| Accent Light | `#BF524B` | `--color-accent-light` | Links, secondary accents |
|
||||
| Text Primary | `#F5F5F5` | `--color-text` | Headlines, primary text |
|
||||
| Text Secondary | `#B0B0B0` | `--color-text-muted` | Body text, descriptions |
|
||||
| Border | `#2A2A2A` | `--color-border` | Subtle borders, dividers |
|
||||
| Success | `#2E7D32` | `--color-success` | Active listings |
|
||||
| Warning | `#F9A825` | `--color-pending` | Pending listings |
|
||||
| Muted | `#757575` | `--color-sold` | Sold listings |
|
||||
|
||||
### 3.3 Typography System
|
||||
|
||||
```css
|
||||
/* Headings */
|
||||
--font-display: 'Abril Fatface', Georgia, serif;
|
||||
|
||||
/* Body */
|
||||
--font-body: 'Inter', 'Droid Sans', Arial, sans-serif;
|
||||
|
||||
/* Scale */
|
||||
--text-xs: 0.75rem; /* 12px */
|
||||
--text-sm: 0.875rem; /* 14px */
|
||||
--text-base: 1rem; /* 16px */
|
||||
--text-lg: 1.125rem; /* 18px */
|
||||
--text-xl: 1.25rem; /* 20px */
|
||||
--text-2xl: 1.5rem; /* 24px */
|
||||
--text-3xl: 1.875rem; /* 30px */
|
||||
--text-4xl: 2.25rem; /* 36px */
|
||||
--text-5xl: 3rem; /* 48px */
|
||||
--text-6xl: 3.75rem; /* 60px */
|
||||
```
|
||||
|
||||
**Recommendation**: Consider upgrading from Droid Sans to Inter for body text - it's more modern, has excellent readability, and better web optimization. Abril Fatface remains perfect for display headings.
|
||||
|
||||
---
|
||||
|
||||
## 4. Page Structure & Layout
|
||||
|
||||
### 4.1 Site Architecture
|
||||
|
||||
```
|
||||
Homepage
|
||||
├── Properties (Listings Archive)
|
||||
│ ├── Property Detail Page (single-property.php)
|
||||
│ └── ...
|
||||
├── About Us
|
||||
│ └── Individual Agent Pages (optional)
|
||||
├── Services (optional)
|
||||
├── Blog/News (archive + single posts)
|
||||
│ └── Blog Post (single.php)
|
||||
├── Contact
|
||||
└── Legal Pages (Privacy Policy, Terms)
|
||||
```
|
||||
|
||||
### 4.2 WordPress Template Hierarchy
|
||||
|
||||
The theme will include the following template files:
|
||||
|
||||
| Template File | Purpose |
|
||||
|---------------|---------|
|
||||
| `front-page.php` | Homepage (static front page) |
|
||||
| `page.php` | Default page template |
|
||||
| `page-contact.php` | Contact page with form + map |
|
||||
| `page-about.php` | About/Team page |
|
||||
| `single.php` | Blog post template |
|
||||
| `single-property.php` | Property detail page |
|
||||
| `archive.php` | Blog archive (news/articles) |
|
||||
| `archive-property.php` | Property listings archive |
|
||||
| `search.php` | Search results |
|
||||
| `404.php` | Not found page |
|
||||
| `header.php` | Global header |
|
||||
| `footer.php` | Global footer |
|
||||
|
||||
### 4.3 Page Templates (User-Selectable)
|
||||
|
||||
These templates will be available in the WordPress page editor:
|
||||
|
||||
| Template Name | File | Use Case |
|
||||
|---------------|------|----------|
|
||||
| Default | `page.php` | Standard content pages |
|
||||
| Full Width | `template-full-width.php` | Pages without sidebar |
|
||||
| Landing Page | `template-landing.php` | Marketing/campaign pages (no header/footer nav) |
|
||||
| Blank Canvas | `template-blank.php` | Full control with block editor |
|
||||
| Content + Sidebar | `template-sidebar.php` | Blog-style layout |
|
||||
|
||||
### 4.2 Homepage Layout (Top to Bottom)
|
||||
|
||||
#### Section 1: Header (Sticky)
|
||||
- Logo (left)
|
||||
- Navigation: Properties | About | Contact (center/right)
|
||||
- Phone number CTA button (right)
|
||||
- Mobile: Hamburger menu
|
||||
|
||||
#### Section 2: Hero
|
||||
- Full-width background image/video
|
||||
- Headline: "Find Your Dream Home Today" (Abril Fatface)
|
||||
- Subheadline: "Expert Real Estate Services for Buyers and Sellers"
|
||||
- Primary CTA: "View Properties" button
|
||||
- Secondary CTA: "Contact Us" button
|
||||
|
||||
#### Section 3: Featured Properties
|
||||
- Section title: "Current Listings"
|
||||
- Filter tabs: All | Residential | Commercial | Land
|
||||
- Property cards in grid (3 columns desktop, 2 tablet, 1 mobile)
|
||||
- "View All Properties" link
|
||||
|
||||
#### Section 4: Why Choose HomeProz
|
||||
- Section title: "Our Mission" or "Why HomeProz"
|
||||
- 3-column feature blocks with icons:
|
||||
- Local Expertise
|
||||
- Personalized Service
|
||||
- Results-Driven
|
||||
- Mission statement text
|
||||
|
||||
#### Section 5: Meet the Team
|
||||
- Section title: "Meet Our Agents"
|
||||
- Agent cards in grid (4 columns desktop)
|
||||
- Each card: Photo, Name, Title, Phone, Email
|
||||
- Hover effect reveals bio snippet
|
||||
|
||||
#### Section 6: Testimonials
|
||||
- Section title: "What Our Clients Say"
|
||||
- Testimonial carousel/slider
|
||||
- Client name and transaction type
|
||||
|
||||
#### Section 7: Contact CTA
|
||||
- Split layout: Form (left) | Map + Info (right)
|
||||
- Contact form fields: Name, Email, Phone, Message
|
||||
- Office address, phone numbers
|
||||
- Embedded Google Map
|
||||
|
||||
#### Section 8: Footer
|
||||
- Logo
|
||||
- Quick links
|
||||
- Contact info
|
||||
- Social media icons
|
||||
- Legal text (copyright, DBA, broker info)
|
||||
|
||||
### 4.3 Properties Archive Page
|
||||
|
||||
- Hero with search bar
|
||||
- Filter sidebar (desktop) / Filter modal (mobile)
|
||||
- Property Type
|
||||
- Price Range
|
||||
- Bedrooms
|
||||
- Status (Active, Pending, Sold)
|
||||
- Location/City
|
||||
- Property grid with pagination
|
||||
- Sort options (Price, Date, etc.)
|
||||
|
||||
### 4.4 Property Detail Page
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ [Breadcrumb: Home > Properties > Address] │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ ┌─────────────────────┐ ┌─────────────────────┐ │
|
||||
│ │ │ │ $XXX,XXX │ │
|
||||
│ │ Main Photo │ │ 123 Main Street │ │
|
||||
│ │ Gallery │ │ City, MN 56007 │ │
|
||||
│ │ │ │ │ │
|
||||
│ │ │ │ 🛏 3 Beds | 🛁 2 Bath │ │
|
||||
│ │ │ │ 📐 1,500 sq ft │ │
|
||||
│ │ │ │ MLS# 12345 │ │
|
||||
│ │ │ │ │ │
|
||||
│ │ [Thumbnail strip] │ │ [Contact Agent] │ │
|
||||
│ └─────────────────────┘ │ [Schedule Showing] │ │
|
||||
│ └─────────────────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Property Description │
|
||||
│ ──────────────────── │
|
||||
│ Lorem ipsum dolor sit amet... │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Features & Amenities │
|
||||
│ ──────────────────── │
|
||||
│ • Feature 1 • Feature 4 • Feature 7 │
|
||||
│ • Feature 2 • Feature 5 • Feature 8 │
|
||||
│ • Feature 3 • Feature 6 • Feature 9 │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Location │
|
||||
│ ──────────────────── │
|
||||
│ [Embedded Google Map] │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Listed By │
|
||||
│ ──────────────────── │
|
||||
│ [Agent Photo] Agent Name | Phone | Email │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 5. Detailed Template Specifications
|
||||
|
||||
### 5.1 Homepage Template (`front-page.php`)
|
||||
|
||||
A modular homepage built with reusable sections. Each section can be toggled on/off via theme options.
|
||||
|
||||
**Sections (in order):**
|
||||
1. Hero Section (full-width image/video + headline + CTAs)
|
||||
2. Featured Properties Grid (3 most recent active listings)
|
||||
3. Value Proposition / Why Choose Us (3-column icon blocks)
|
||||
4. About Preview (brief intro + link to About page)
|
||||
5. Team Preview (agent cards grid)
|
||||
6. Testimonials Carousel
|
||||
7. Contact CTA Section (form + map)
|
||||
8. Footer
|
||||
|
||||
### 5.2 Default Page Template (`page.php`)
|
||||
|
||||
Standard content page with consistent structure:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ HEADER │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Page Hero (optional) │
|
||||
│ ┌─────────────────────────────────────────────┐ │
|
||||
│ │ Page Title (h1) │ │
|
||||
│ │ Optional subtitle/breadcrumb │ │
|
||||
│ └─────────────────────────────────────────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Content Area │
|
||||
│ ┌─────────────────────────────────────────────┐ │
|
||||
│ │ │ │
|
||||
│ │ Block Editor Content │ │
|
||||
│ │ (constrained width: 800px max) │ │
|
||||
│ │ │ │
|
||||
│ └─────────────────────────────────────────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ FOOTER │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
**Features:**
|
||||
- Clean, readable content width (65-75 characters per line)
|
||||
- Supports all core WordPress blocks
|
||||
- Optional featured image as page hero
|
||||
- Breadcrumb navigation
|
||||
|
||||
### 5.3 Full Width Template (`template-full-width.php`)
|
||||
|
||||
For pages that need edge-to-edge content:
|
||||
|
||||
**Use Cases:**
|
||||
- Image galleries
|
||||
- Portfolio pages
|
||||
- Pages with custom layouts via blocks
|
||||
- Wide comparison tables
|
||||
|
||||
**Differences from Default:**
|
||||
- No max-width constraint on content
|
||||
- Full-bleed image support
|
||||
- Better for Gutenberg group blocks with backgrounds
|
||||
|
||||
### 5.4 Landing Page Template (`template-landing.php`)
|
||||
|
||||
Distraction-free template for marketing campaigns:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ Minimal Header (logo only, no nav) │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ │
|
||||
│ FULL CONTENT AREA │
|
||||
│ (no sidebar, focused design) │
|
||||
│ │
|
||||
│ Designed for conversion: │
|
||||
│ - Hero with single CTA │
|
||||
│ - Benefits list │
|
||||
│ - Social proof │
|
||||
│ - Form or contact CTA │
|
||||
│ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Minimal Footer (legal links only) │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
**Use Cases:**
|
||||
- Property-specific landing pages
|
||||
- Seasonal promotions ("Spring Listings!")
|
||||
- Buyer/Seller guides with lead capture
|
||||
- Ad campaign destinations
|
||||
|
||||
### 5.5 About/Team Page Template (`page-about.php`)
|
||||
|
||||
Specialized template for company and team information:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ HEADER │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Page Hero with Company Photo │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Company Story Section │
|
||||
│ (Block editor content area) │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Our Values / Mission │
|
||||
│ (3-column layout with icons) │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Meet the Team │
|
||||
│ ┌─────┐ ┌─────┐ ┌─────┐ ┌─────┐ │
|
||||
│ │Agent│ │Agent│ │Agent│ │Agent│ │
|
||||
│ │Card │ │Card │ │Card │ │Card │ │
|
||||
│ └─────┘ └─────┘ └─────┘ └─────┘ │
|
||||
│ (Auto-populated from Team CPT or ACF) │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Broker Information │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Contact CTA │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ FOOTER │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
### 5.6 Contact Page Template (`page-contact.php`)
|
||||
|
||||
Dedicated contact page with form and location info:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ HEADER │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ "Get In Touch" Hero │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ ┌───────────────────┐ ┌───────────────────────┐ │
|
||||
│ │ │ │ │ │
|
||||
│ │ Contact Form │ │ Contact Info │ │
|
||||
│ │ │ │ - Address │ │
|
||||
│ │ Name │ │ - Phone │ │
|
||||
│ │ Email │ │ - Email │ │
|
||||
│ │ Phone │ │ - Hours │ │
|
||||
│ │ Message │ │ │ │
|
||||
│ │ │ │ [Google Map] │ │
|
||||
│ │ [Send Message] │ │ │ │
|
||||
│ │ │ │ │ │
|
||||
│ └───────────────────┘ └───────────────────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Additional Content (optional) │
|
||||
│ (Block editor area for FAQs, etc.) │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ FOOTER │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
### 5.7 Property Archive Template (`archive-property.php`)
|
||||
|
||||
Listings page with search and filters:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ HEADER │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Hero: "Browse Our Properties" │
|
||||
│ [Search Bar] │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Filter Bar │
|
||||
│ [Type ▼] [Price ▼] [Beds ▼] [Status ▼] [Clear] │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Results: XX Properties Found [Sort: Recent ▼]│
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
|
||||
│ │Property │ │Property │ │Property │ │
|
||||
│ │ Card │ │ Card │ │ Card │ │
|
||||
│ └─────────┘ └─────────┘ └─────────┘ │
|
||||
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
|
||||
│ │Property │ │Property │ │Property │ │
|
||||
│ │ Card │ │ Card │ │ Card │ │
|
||||
│ └─────────┘ └─────────┘ └─────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Pagination: [< Prev] [1] [2] [3] [Next >] │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ FOOTER │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
**Filter Options:**
|
||||
- Property Type: Residential, Commercial, Land, Multi-Family
|
||||
- Price Range: Slider or preset ranges
|
||||
- Bedrooms: Any, 1+, 2+, 3+, 4+
|
||||
- Bathrooms: Any, 1+, 2+, 3+
|
||||
- Status: Active, Pending, Sold, All
|
||||
- Location/City: Dropdown of available cities
|
||||
|
||||
### 5.8 Single Property Template (`single-property.php`)
|
||||
|
||||
Detailed property view (see Section 4.6 for layout).
|
||||
|
||||
**Key Features:**
|
||||
- Photo gallery with lightbox
|
||||
- Property details sidebar (sticky on scroll)
|
||||
- Tabbed content: Description | Features | Location
|
||||
- Agent contact card
|
||||
- Related/Similar properties
|
||||
- Share buttons
|
||||
- Print-friendly version option
|
||||
|
||||
### 5.9 Blog Archive Template (`archive.php`)
|
||||
|
||||
Blog/News listing page:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ HEADER │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Hero: "News & Insights" │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ ┌──────────────────────┐ ┌──────────────────┐ │
|
||||
│ │ │ │ Sidebar │ │
|
||||
│ │ Post Cards Grid │ │ - Search │ │
|
||||
│ │ ┌──────┐ ┌──────┐ │ │ - Categories │ │
|
||||
│ │ │ Post │ │ Post │ │ │ - Recent Posts │ │
|
||||
│ │ └──────┘ └──────┘ │ │ - Contact CTA │ │
|
||||
│ │ ┌──────┐ ┌──────┐ │ │ │ │
|
||||
│ │ │ Post │ │ Post │ │ │ │ │
|
||||
│ │ └──────┘ └──────┘ │ │ │ │
|
||||
│ │ │ │ │ │
|
||||
│ └──────────────────────┘ └──────────────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Pagination │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ FOOTER │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
**Post Card Design:**
|
||||
- Featured image (16:9)
|
||||
- Category tag
|
||||
- Post title
|
||||
- Excerpt (2-3 lines)
|
||||
- Date + Read time
|
||||
- "Read More" link
|
||||
|
||||
### 5.10 Blog Post Template (`single.php`)
|
||||
|
||||
Blog/news article page:
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────┐
|
||||
│ HEADER │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Featured Image (full-width) │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ ┌─────────────────────────────────────────────┐ │
|
||||
│ │ Post Title (h1) │ │
|
||||
│ │ Date | Author | Category │ │
|
||||
│ └─────────────────────────────────────────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ ┌──────────────────────┐ ┌──────────────────┐ │
|
||||
│ │ │ │ Sidebar │ │
|
||||
│ │ Post Content │ │ - Search │ │
|
||||
│ │ (Block editor) │ │ - Categories │ │
|
||||
│ │ │ │ - Recent Posts │ │
|
||||
│ │ │ │ - Contact CTA │ │
|
||||
│ │ │ │ │ │
|
||||
│ └──────────────────────┘ └──────────────────┘ │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Author Bio Box │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ Related Posts (3 cards) │
|
||||
├─────────────────────────────────────────────────┤
|
||||
│ FOOTER │
|
||||
└─────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
### 5.11 404 Page Template (`404.php`)
|
||||
|
||||
User-friendly error page:
|
||||
|
||||
- Friendly message: "Oops! Page not found"
|
||||
- Search bar
|
||||
- Quick links to: Home, Properties, Contact
|
||||
- Recent/Featured properties
|
||||
- Maintains brand styling
|
||||
|
||||
### 5.12 Search Results Template (`search.php`)
|
||||
|
||||
- Shows results from all searchable content
|
||||
- Filters by content type (Pages, Properties, Posts)
|
||||
- Property results show as cards
|
||||
- Page/Post results show as list items
|
||||
|
||||
---
|
||||
|
||||
## 6. Block Patterns (Reusable Layouts)
|
||||
|
||||
Pre-built block patterns for the client to easily create consistent content:
|
||||
|
||||
### 6.1 Content Patterns
|
||||
|
||||
| Pattern Name | Description |
|
||||
|--------------|-------------|
|
||||
| Hero with CTA | Full-width hero with heading, text, and buttons |
|
||||
| Feature Grid (3-col) | Three columns with icons, headings, and text |
|
||||
| Feature Grid (4-col) | Four columns with icons, headings, and text |
|
||||
| Team Member Card | Single agent/team member display |
|
||||
| Testimonial | Quote with attribution |
|
||||
| Testimonial Carousel | Multiple testimonials in slider |
|
||||
| Stats/Numbers Row | Key statistics with large numbers |
|
||||
| Split Content | Image on one side, text on other |
|
||||
| CTA Banner | Full-width call-to-action section |
|
||||
| FAQ Accordion | Expandable question/answer pairs |
|
||||
| Contact Info Block | Address, phone, email, hours |
|
||||
| Image Gallery | Grid of images with lightbox |
|
||||
| Price Table | Compare service tiers (if needed) |
|
||||
|
||||
### 6.2 Property-Specific Patterns
|
||||
|
||||
| Pattern Name | Description |
|
||||
|--------------|-------------|
|
||||
| Featured Property | Single property highlight |
|
||||
| Property Grid (3) | Three property cards in a row |
|
||||
| Property Carousel | Scrollable property showcase |
|
||||
| Property Search Bar | Search input with filters |
|
||||
|
||||
---
|
||||
|
||||
## 7. Component Design Specifications
|
||||
|
||||
### 7.1 Property Card
|
||||
|
||||
```
|
||||
┌──────────────────────────────┐
|
||||
│ [STATUS BADGE: ACTIVE] │
|
||||
│ ┌──────────────────────────┐ │
|
||||
│ │ │ │
|
||||
│ │ Property Image │ │
|
||||
│ │ (16:10 ratio) │ │
|
||||
│ │ │ │
|
||||
│ └──────────────────────────┘ │
|
||||
│ $XXX,XXX │
|
||||
│ 123 Main Street │
|
||||
│ City, MN 56007 │
|
||||
│ │
|
||||
│ 🛏 3 🛁 2 📐 1,500 sqft │
|
||||
│ │
|
||||
│ [View Details →] │
|
||||
└──────────────────────────────┘
|
||||
```
|
||||
|
||||
**Specifications:**
|
||||
- Card background: `#161616`
|
||||
- Border radius: 8px
|
||||
- Image aspect ratio: 16:10 (better for real estate)
|
||||
- Hover effect: Slight scale (1.02) + shadow
|
||||
- Status badge colors:
|
||||
- Active: Green (`#2E7D32`)
|
||||
- Pending: Yellow (`#F9A825`)
|
||||
- Sold: Gray (`#757575`)
|
||||
|
||||
### 7.2 Agent Card
|
||||
|
||||
```
|
||||
┌──────────────────────────────┐
|
||||
│ ┌──────────────────────────┐ │
|
||||
│ │ │ │
|
||||
│ │ Agent Photo │ │
|
||||
│ │ (Square, rounded) │ │
|
||||
│ │ │ │
|
||||
│ └──────────────────────────┘ │
|
||||
│ │
|
||||
│ Agent Name │
|
||||
│ REALTOR® │
|
||||
│ │
|
||||
│ 📞 507-XXX-XXXX │
|
||||
│ ✉️ email@homeproz.com │
|
||||
└──────────────────────────────┘
|
||||
```
|
||||
|
||||
### 7.3 Buttons
|
||||
|
||||
**Primary Button:**
|
||||
- Background: `#9F3730`
|
||||
- Text: `#FFFFFF`
|
||||
- Padding: 16px 32px
|
||||
- Border radius: 4px
|
||||
- Hover: `#C8473F`
|
||||
- Transition: 0.3s ease
|
||||
|
||||
**Secondary Button:**
|
||||
- Background: transparent
|
||||
- Border: 2px solid `#9F3730`
|
||||
- Text: `#9F3730`
|
||||
- Hover: Fill with `#9F3730`, text white
|
||||
|
||||
### 7.4 Form Fields
|
||||
|
||||
- Background: `#161616`
|
||||
- Border: 1px solid `#2A2A2A`
|
||||
- Border on focus: `#9F3730`
|
||||
- Text color: `#F5F5F5`
|
||||
- Placeholder: `#757575`
|
||||
- Border radius: 4px
|
||||
- Padding: 16px
|
||||
|
||||
---
|
||||
|
||||
## 6. Responsive Breakpoints
|
||||
|
||||
```css
|
||||
/* Mobile First */
|
||||
--breakpoint-sm: 640px; /* Large phones */
|
||||
--breakpoint-md: 768px; /* Tablets */
|
||||
--breakpoint-lg: 1024px; /* Desktop */
|
||||
--breakpoint-xl: 1280px; /* Large desktop */
|
||||
--breakpoint-2xl: 1536px; /* Extra large */
|
||||
```
|
||||
|
||||
### Layout Behavior
|
||||
|
||||
| Element | Mobile | Tablet | Desktop |
|
||||
|---------|--------|--------|---------|
|
||||
| Property Grid | 1 col | 2 col | 3 col |
|
||||
| Agent Grid | 1 col | 2 col | 4 col |
|
||||
| Nav | Hamburger | Hamburger | Full |
|
||||
| Hero CTA | Stacked | Side-by-side | Side-by-side |
|
||||
| Contact Section | Stacked | Split | Split |
|
||||
|
||||
---
|
||||
|
||||
## 7. Imagery Guidelines
|
||||
|
||||
### 7.1 Property Photos
|
||||
- Aspect ratio: 16:10 for cards, flexible for galleries
|
||||
- Minimum resolution: 1200px wide
|
||||
- Format: WebP with JPEG fallback
|
||||
- Optimization: Lazy loading, responsive srcset
|
||||
|
||||
### 7.2 Agent Photos
|
||||
- Aspect ratio: 1:1 (square)
|
||||
- Style: Professional headshot, neutral background
|
||||
- Minimum resolution: 400x400px
|
||||
- Treatment: Slight rounded corners (8px) or circular
|
||||
|
||||
### 7.3 Hero Images
|
||||
- Full-width, high-resolution
|
||||
- Consider: Local landmarks, beautiful homes, team photos
|
||||
- Overlay: Dark gradient for text readability
|
||||
|
||||
---
|
||||
|
||||
## 8. Animation & Interaction
|
||||
|
||||
### 8.1 Micro-interactions
|
||||
- Button hover: Color transition (0.3s)
|
||||
- Card hover: Scale (1.02) + shadow
|
||||
- Link hover: Color transition + underline
|
||||
- Form focus: Border color change
|
||||
|
||||
### 8.2 Page Transitions
|
||||
- Fade in on scroll (intersection observer)
|
||||
- Stagger effect for card grids
|
||||
- Smooth scroll for anchor links
|
||||
|
||||
### 8.3 Loading States
|
||||
- Skeleton screens for property cards
|
||||
- Spinner for form submission
|
||||
- Progressive image loading
|
||||
|
||||
---
|
||||
|
||||
## 9. Accessibility Considerations
|
||||
|
||||
- Minimum contrast ratio: 4.5:1 for text
|
||||
- Focus states: Visible outline on all interactive elements
|
||||
- Skip to content link
|
||||
- Proper heading hierarchy (h1 > h2 > h3)
|
||||
- Alt text for all images
|
||||
- ARIA labels where needed
|
||||
- Keyboard navigation support
|
||||
|
||||
---
|
||||
|
||||
## 10. SEO & Performance
|
||||
|
||||
### 10.1 Technical SEO
|
||||
- Semantic HTML structure
|
||||
- Schema.org markup for:
|
||||
- RealEstateAgent
|
||||
- RealEstateListing
|
||||
- LocalBusiness
|
||||
- XML sitemap
|
||||
- Optimized meta tags per page
|
||||
- Open Graph tags for social sharing
|
||||
|
||||
### 10.2 Performance Targets
|
||||
- Lighthouse score: 90+ (Performance)
|
||||
- First Contentful Paint: < 1.5s
|
||||
- Largest Contentful Paint: < 2.5s
|
||||
- Cumulative Layout Shift: < 0.1
|
||||
|
||||
---
|
||||
|
||||
## 11. Design Mockup References
|
||||
|
||||
Screenshots of current site saved to:
|
||||
- `site_analysis/homepage-full.png` - Full page capture
|
||||
- `site_analysis/homepage-viewport.png` - Above the fold
|
||||
|
||||
---
|
||||
|
||||
## 12. Open Questions for Client Discussion
|
||||
|
||||
1. **Hero Media**: Prefer static image or video background?
|
||||
2. **Team Page**: Individual agent bio pages, or keep on single page?
|
||||
3. **Blog/News**: Future consideration for content marketing?
|
||||
4. **Testimonials**: Have text testimonials ready, or need to collect?
|
||||
5. **Photo Gallery**: Keep existing gallery section, or integrate into properties?
|
||||
6. **Logo**: Current logo is from business card - do you have vector/high-res version?
|
||||
|
||||
---
|
||||
|
||||
## 13. Approval
|
||||
|
||||
This design document is a draft for review. Please provide feedback on:
|
||||
- Color palette refinements
|
||||
- Page structure and sections
|
||||
- Component designs
|
||||
- Any missing elements
|
||||
|
||||
---
|
||||
|
||||
*Document Version: 1.0*
|
||||
*Date: November 28, 2025*
|
||||
*Prepared by: Hanson.xyz Development Team*
|
||||
@@ -0,0 +1,679 @@
|
||||
# HomeProz WordPress Website Implementation Plan
|
||||
## Draft v1.0 - For Review
|
||||
|
||||
---
|
||||
|
||||
## 1. Executive Summary
|
||||
|
||||
This document outlines the implementation approach for building the HomeProz WordPress website. The project will deliver a custom WordPress theme with Advanced Custom Fields (ACF) integration for property management, following modern WordPress development best practices.
|
||||
|
||||
**Estimated Development Time:** 40 hours (as per contract)
|
||||
**Approach:** Custom theme development with ACF Pro for property listings
|
||||
|
||||
---
|
||||
|
||||
## 2. Technology Stack
|
||||
|
||||
### 2.1 Core Platform
|
||||
| Component | Technology | Version |
|
||||
|-----------|------------|---------|
|
||||
| CMS | WordPress | 6.x (latest stable) |
|
||||
| PHP | PHP | 8.1+ |
|
||||
| Database | MySQL/MariaDB | 8.0+ / 10.6+ |
|
||||
| Web Server | Nginx or Apache | Latest |
|
||||
|
||||
### 2.2 Theme Development
|
||||
| Component | Technology | Notes |
|
||||
|-----------|------------|-------|
|
||||
| Base Theme | Custom theme from scratch | No parent theme dependency |
|
||||
| CSS | Modern CSS with CSS Variables | No preprocessor needed |
|
||||
| JavaScript | Vanilla JS + Alpine.js | Lightweight interactivity |
|
||||
| Build Tools | None required | Keep it simple |
|
||||
| Block Editor | Full support | theme.json configuration |
|
||||
|
||||
### 2.3 Required Plugins
|
||||
| Plugin | Purpose | License |
|
||||
|--------|---------|---------|
|
||||
| Advanced Custom Fields Pro | Property fields & flexible content | Paid ($49/yr) |
|
||||
| Contact Form 7 or WPForms Lite | Contact forms | Free |
|
||||
| Yoast SEO or Rank Math | SEO management | Free |
|
||||
| WP Super Cache or LiteSpeed Cache | Caching | Free |
|
||||
| Wordfence or Sucuri | Security | Free tier |
|
||||
| UpdraftPlus | Backups | Free |
|
||||
|
||||
### 2.4 Optional/Recommended Plugins
|
||||
| Plugin | Purpose | When to Add |
|
||||
|--------|---------|-------------|
|
||||
| Imagify or ShortPixel | Image optimization | At launch |
|
||||
| Redirection | URL redirects | If migrating |
|
||||
| Google Site Kit | Analytics integration | Post-launch |
|
||||
|
||||
---
|
||||
|
||||
## 3. Project Structure
|
||||
|
||||
### 3.1 Theme File Structure
|
||||
|
||||
```
|
||||
themes/homeproz/
|
||||
├── assets/
|
||||
│ ├── css/
|
||||
│ │ ├── style.css # Main compiled styles
|
||||
│ │ ├── editor-style.css # Block editor styles
|
||||
│ │ └── components/
|
||||
│ │ ├── buttons.css
|
||||
│ │ ├── cards.css
|
||||
│ │ ├── forms.css
|
||||
│ │ └── navigation.css
|
||||
│ ├── js/
|
||||
│ │ ├── main.js # Main scripts
|
||||
│ │ ├── navigation.js # Mobile menu
|
||||
│ │ └── property-filter.js # AJAX filtering
|
||||
│ ├── images/
|
||||
│ │ ├── logo.svg
|
||||
│ │ └── placeholder.jpg
|
||||
│ └── fonts/ # If self-hosting
|
||||
│
|
||||
├── inc/
|
||||
│ ├── acf-fields.php # ACF field group definitions
|
||||
│ ├── custom-post-types.php # Property CPT registration
|
||||
│ ├── enqueue.php # Script/style enqueuing
|
||||
│ ├── theme-setup.php # Theme supports, menus, etc.
|
||||
│ ├── template-functions.php # Helper functions
|
||||
│ ├── block-patterns.php # Custom block patterns
|
||||
│ └── customizer.php # Theme options (if needed)
|
||||
│
|
||||
├── template-parts/
|
||||
│ ├── header/
|
||||
│ │ ├── site-header.php
|
||||
│ │ └── navigation.php
|
||||
│ ├── footer/
|
||||
│ │ ├── site-footer.php
|
||||
│ │ └── footer-widgets.php
|
||||
│ ├── content/
|
||||
│ │ ├── content-page.php
|
||||
│ │ ├── content-post.php
|
||||
│ │ └── content-none.php
|
||||
│ ├── property/
|
||||
│ │ ├── property-card.php
|
||||
│ │ ├── property-gallery.php
|
||||
│ │ ├── property-details.php
|
||||
│ │ ├── property-filters.php
|
||||
│ │ └── property-agent.php
|
||||
│ ├── components/
|
||||
│ │ ├── agent-card.php
|
||||
│ │ ├── testimonial.php
|
||||
│ │ ├── cta-section.php
|
||||
│ │ └── hero-section.php
|
||||
│ └── blocks/ # Custom block templates
|
||||
│
|
||||
├── patterns/ # Block patterns (WP 6.0+)
|
||||
│ ├── hero-cta.php
|
||||
│ ├── feature-grid.php
|
||||
│ └── team-grid.php
|
||||
│
|
||||
├── templates/ # Full Site Editing templates (optional)
|
||||
│
|
||||
├── 404.php
|
||||
├── archive.php
|
||||
├── archive-property.php
|
||||
├── footer.php
|
||||
├── front-page.php
|
||||
├── functions.php
|
||||
├── header.php
|
||||
├── index.php
|
||||
├── page.php
|
||||
├── page-about.php
|
||||
├── page-contact.php
|
||||
├── search.php
|
||||
├── single.php
|
||||
├── single-property.php
|
||||
├── sidebar.php
|
||||
├── template-full-width.php
|
||||
├── template-landing.php
|
||||
├── template-blank.php
|
||||
├── screenshot.png
|
||||
├── style.css
|
||||
└── theme.json # Block editor config
|
||||
```
|
||||
|
||||
### 3.2 ACF Field Structure
|
||||
|
||||
#### Property Fields Group
|
||||
```
|
||||
Property Details
|
||||
├── Basic Information
|
||||
│ ├── property_status (select: Active, Pending, Sold)
|
||||
│ ├── property_type (select: Residential, Commercial, Land, Multi-Family)
|
||||
│ ├── price (number)
|
||||
│ ├── price_display (text) - for "Call for Price" etc.
|
||||
│ └── mls_number (text)
|
||||
│
|
||||
├── Address
|
||||
│ ├── street_address (text)
|
||||
│ ├── city (text)
|
||||
│ ├── state (text, default: MN)
|
||||
│ ├── zip_code (text)
|
||||
│ └── google_maps_embed (textarea) - or use lat/lng
|
||||
│
|
||||
├── Property Specs
|
||||
│ ├── bedrooms (number)
|
||||
│ ├── bathrooms (number)
|
||||
│ ├── square_feet (number)
|
||||
│ ├── lot_size (text)
|
||||
│ ├── year_built (number)
|
||||
│ └── garage (select: None, 1-car, 2-car, 3+car)
|
||||
│
|
||||
├── Media
|
||||
│ ├── featured_image (uses WP featured image)
|
||||
│ ├── gallery (gallery field)
|
||||
│ └── virtual_tour_url (url) - optional
|
||||
│
|
||||
├── Description
|
||||
│ ├── short_description (textarea) - for cards
|
||||
│ └── full_description (wysiwyg)
|
||||
│
|
||||
├── Features & Amenities
|
||||
│ └── features (checkbox or repeater)
|
||||
│
|
||||
└── Agent Assignment
|
||||
└── listing_agent (post object -> Agent CPT or user select)
|
||||
```
|
||||
|
||||
#### Agent/Team Member Fields
|
||||
```
|
||||
Agent Details
|
||||
├── agent_title (text) - "REALTOR®"
|
||||
├── agent_phone (text)
|
||||
├── agent_email (email)
|
||||
├── agent_bio (wysiwyg)
|
||||
├── agent_photo (image)
|
||||
└── agent_social (repeater: platform, url)
|
||||
```
|
||||
|
||||
#### Testimonials Fields
|
||||
```
|
||||
Testimonial Details
|
||||
├── testimonial_text (textarea)
|
||||
├── client_name (text)
|
||||
├── client_location (text)
|
||||
├── transaction_type (select: Buyer, Seller, Both)
|
||||
└── rating (number 1-5) - optional
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 4. Implementation Phases
|
||||
|
||||
### Phase 1: Foundation (Day 1-2)
|
||||
**Estimated: 8 hours**
|
||||
|
||||
- [ ] Set up local development environment
|
||||
- [ ] Create theme folder structure
|
||||
- [ ] Set up `functions.php` with includes
|
||||
- [ ] Configure `theme.json` for block editor
|
||||
- [ ] Create `style.css` with CSS variables (colors, typography)
|
||||
- [ ] Build `header.php` with navigation
|
||||
- [ ] Build `footer.php` with widgets areas
|
||||
- [ ] Create basic `index.php`, `page.php`
|
||||
- [ ] Register menus (Primary, Footer)
|
||||
- [ ] Set up theme supports (thumbnails, title-tag, etc.)
|
||||
|
||||
**Deliverable:** Basic theme framework with header/footer
|
||||
|
||||
### Phase 2: Property System (Day 3-4)
|
||||
**Estimated: 10 hours**
|
||||
|
||||
- [ ] Register Property custom post type
|
||||
- [ ] Install and configure ACF Pro
|
||||
- [ ] Create Property field groups
|
||||
- [ ] Build `archive-property.php` (listings page)
|
||||
- [ ] Build `single-property.php` (detail page)
|
||||
- [ ] Create `property-card.php` template part
|
||||
- [ ] Create `property-gallery.php` template part
|
||||
- [ ] Create `property-filters.php` template part
|
||||
- [ ] Implement AJAX filtering (property-filter.js)
|
||||
- [ ] Add property status badges
|
||||
- [ ] Test property CRUD in admin
|
||||
|
||||
**Deliverable:** Fully functional property listing system
|
||||
|
||||
### Phase 3: Page Templates (Day 4-5)
|
||||
**Estimated: 8 hours**
|
||||
|
||||
- [ ] Build `front-page.php` (homepage sections)
|
||||
- [ ] Build `page-about.php` (about/team page)
|
||||
- [ ] Build `page-contact.php` (contact page)
|
||||
- [ ] Build `archive.php` (blog listing)
|
||||
- [ ] Build `single.php` (blog post)
|
||||
- [ ] Create `template-full-width.php`
|
||||
- [ ] Create `template-landing.php`
|
||||
- [ ] Build `404.php`
|
||||
- [ ] Build `search.php`
|
||||
- [ ] Create reusable template parts:
|
||||
- [ ] Hero section
|
||||
- [ ] CTA section
|
||||
- [ ] Testimonial component
|
||||
- [ ] Agent card component
|
||||
- [ ] Post card component
|
||||
- [ ] Sidebar widgets
|
||||
- [ ] Set up Contact Form 7 / form plugin
|
||||
|
||||
**Deliverable:** All page templates functional (including blog)
|
||||
|
||||
### Phase 4: Block Patterns & Polish (Day 5-6)
|
||||
**Estimated: 6 hours**
|
||||
|
||||
- [ ] Create block patterns:
|
||||
- [ ] Hero with CTA
|
||||
- [ ] Feature grid (3-col)
|
||||
- [ ] Team grid
|
||||
- [ ] Testimonial
|
||||
- [ ] Split content
|
||||
- [ ] CTA banner
|
||||
- [ ] Add editor styles (`editor-style.css`)
|
||||
- [ ] Ensure block editor matches frontend
|
||||
- [ ] Add responsive styles (mobile, tablet)
|
||||
- [ ] Implement animations/transitions
|
||||
- [ ] Cross-browser testing
|
||||
|
||||
**Deliverable:** Polished theme with reusable patterns
|
||||
|
||||
### Phase 5: Content & SEO (Day 6-7)
|
||||
**Estimated: 4 hours**
|
||||
|
||||
- [ ] Install and configure Yoast/Rank Math
|
||||
- [ ] Add Schema.org markup:
|
||||
- [ ] RealEstateAgent
|
||||
- [ ] RealEstateListing
|
||||
- [ ] LocalBusiness
|
||||
- [ ] Set up XML sitemap
|
||||
- [ ] Configure Open Graph meta tags
|
||||
- [ ] Add favicon and touch icons
|
||||
- [ ] Enter initial content:
|
||||
- [ ] Homepage content
|
||||
- [ ] About page content
|
||||
- [ ] Contact info
|
||||
- [ ] Sample properties (for testing)
|
||||
- [ ] Add team member data
|
||||
|
||||
**Deliverable:** SEO-ready site with initial content
|
||||
|
||||
### Phase 6: Performance & Security (Day 7)
|
||||
**Estimated: 2 hours**
|
||||
|
||||
- [ ] Install caching plugin
|
||||
- [ ] Configure image optimization
|
||||
- [ ] Enable GZIP compression
|
||||
- [ ] Set up lazy loading
|
||||
- [ ] Install security plugin
|
||||
- [ ] Configure SSL/HTTPS
|
||||
- [ ] Set up automated backups
|
||||
- [ ] Run Lighthouse audit
|
||||
- [ ] Address any performance issues
|
||||
|
||||
**Deliverable:** Optimized, secure site
|
||||
|
||||
### Phase 7: Testing & Training (Day 7-8)
|
||||
**Estimated: 2 hours**
|
||||
|
||||
- [ ] Full QA testing:
|
||||
- [ ] All pages render correctly
|
||||
- [ ] Forms submit properly
|
||||
- [ ] Properties filter/search works
|
||||
- [ ] Mobile responsiveness
|
||||
- [ ] Cross-browser (Chrome, Firefox, Safari, Edge)
|
||||
- [ ] Create documentation
|
||||
- [ ] Conduct training session (1-2 hours)
|
||||
- [ ] Client review on staging
|
||||
|
||||
**Deliverable:** Tested site ready for launch
|
||||
|
||||
---
|
||||
|
||||
## 5. Custom Post Types & Taxonomies
|
||||
|
||||
### 5.1 Property CPT
|
||||
|
||||
```php
|
||||
// Registration in custom-post-types.php
|
||||
register_post_type('property', [
|
||||
'labels' => [
|
||||
'name' => 'Properties',
|
||||
'singular_name' => 'Property',
|
||||
'add_new' => 'Add New Property',
|
||||
'add_new_item' => 'Add New Property',
|
||||
'edit_item' => 'Edit Property',
|
||||
'view_item' => 'View Property',
|
||||
'search_items' => 'Search Properties',
|
||||
'not_found' => 'No properties found',
|
||||
],
|
||||
'public' => true,
|
||||
'has_archive' => true,
|
||||
'rewrite' => ['slug' => 'properties'],
|
||||
'menu_icon' => 'dashicons-building',
|
||||
'supports' => ['title', 'editor', 'thumbnail', 'excerpt'],
|
||||
'show_in_rest' => true, // Enable block editor
|
||||
]);
|
||||
```
|
||||
|
||||
### 5.2 Property Taxonomies
|
||||
|
||||
```php
|
||||
// Property Type
|
||||
register_taxonomy('property_type', 'property', [
|
||||
'labels' => ['name' => 'Property Types'],
|
||||
'hierarchical' => true,
|
||||
'rewrite' => ['slug' => 'property-type'],
|
||||
'show_in_rest' => true,
|
||||
]);
|
||||
|
||||
// Property Status (or use ACF field)
|
||||
register_taxonomy('property_status', 'property', [
|
||||
'labels' => ['name' => 'Status'],
|
||||
'hierarchical' => true,
|
||||
'rewrite' => ['slug' => 'status'],
|
||||
'show_in_rest' => true,
|
||||
]);
|
||||
|
||||
// Location/City
|
||||
register_taxonomy('property_location', 'property', [
|
||||
'labels' => ['name' => 'Locations'],
|
||||
'hierarchical' => true,
|
||||
'rewrite' => ['slug' => 'location'],
|
||||
'show_in_rest' => true,
|
||||
]);
|
||||
```
|
||||
|
||||
### 5.3 Agent CPT (Optional)
|
||||
|
||||
If managing agents as posts rather than ACF options:
|
||||
|
||||
```php
|
||||
register_post_type('agent', [
|
||||
'labels' => ['name' => 'Agents', 'singular_name' => 'Agent'],
|
||||
'public' => true,
|
||||
'has_archive' => true,
|
||||
'rewrite' => ['slug' => 'agents'],
|
||||
'menu_icon' => 'dashicons-id-alt',
|
||||
'supports' => ['title', 'thumbnail'],
|
||||
'show_in_rest' => true,
|
||||
]);
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 6. Key Features Implementation
|
||||
|
||||
### 6.1 Property Search & Filter
|
||||
|
||||
**Approach:** AJAX-based filtering without page reload
|
||||
|
||||
```javascript
|
||||
// property-filter.js (simplified)
|
||||
document.addEventListener('DOMContentLoaded', function() {
|
||||
const filterForm = document.querySelector('.property-filters');
|
||||
|
||||
filterForm.addEventListener('change', function() {
|
||||
const formData = new FormData(filterForm);
|
||||
formData.append('action', 'filter_properties');
|
||||
|
||||
fetch(ajaxurl, {
|
||||
method: 'POST',
|
||||
body: formData
|
||||
})
|
||||
.then(response => response.json())
|
||||
.then(data => {
|
||||
document.querySelector('.property-grid').innerHTML = data.html;
|
||||
document.querySelector('.results-count').textContent = data.count;
|
||||
});
|
||||
});
|
||||
});
|
||||
```
|
||||
|
||||
### 6.2 Property Gallery
|
||||
|
||||
**Approach:** Lightbox gallery using Fancybox or similar
|
||||
|
||||
- Thumbnail grid below main image
|
||||
- Click to open lightbox
|
||||
- Swipe support on mobile
|
||||
- Lazy loading for performance
|
||||
|
||||
### 6.3 Agent Assignment
|
||||
|
||||
Properties link to agents for "Listed By" section:
|
||||
- ACF relationship field connecting Property -> Agent
|
||||
- Display agent card on single property page
|
||||
- Click to contact or view agent profile
|
||||
|
||||
### 6.4 Contact Form
|
||||
|
||||
Using Contact Form 7 or WPForms:
|
||||
- Standard contact form (Name, Email, Phone, Message)
|
||||
- Property inquiry form (includes property reference)
|
||||
- Email notifications to appropriate agent
|
||||
|
||||
### 6.5 Map Integration
|
||||
|
||||
Options:
|
||||
1. **Google Maps Embed** (simple, free) - paste embed code per property
|
||||
2. **Google Maps API** (interactive) - requires API key, more setup
|
||||
3. **Leaflet/OpenStreetMap** (free, no API key) - good alternative
|
||||
|
||||
Recommendation: Start with embed codes, upgrade to API if needed.
|
||||
|
||||
---
|
||||
|
||||
## 7. Theme Customization Options
|
||||
|
||||
### 7.1 theme.json Configuration
|
||||
|
||||
```json
|
||||
{
|
||||
"$schema": "https://schemas.wp.org/trunk/theme.json",
|
||||
"version": 2,
|
||||
"settings": {
|
||||
"color": {
|
||||
"palette": [
|
||||
{ "slug": "primary", "color": "#9F3730", "name": "Primary" },
|
||||
{ "slug": "primary-dark", "color": "#0A0A0A", "name": "Background" },
|
||||
{ "slug": "text", "color": "#F5F5F5", "name": "Text" },
|
||||
{ "slug": "text-muted", "color": "#B0B0B0", "name": "Text Muted" }
|
||||
]
|
||||
},
|
||||
"typography": {
|
||||
"fontFamilies": [
|
||||
{
|
||||
"fontFamily": "'Abril Fatface', Georgia, serif",
|
||||
"slug": "display",
|
||||
"name": "Display"
|
||||
},
|
||||
{
|
||||
"fontFamily": "'Inter', 'Droid Sans', Arial, sans-serif",
|
||||
"slug": "body",
|
||||
"name": "Body"
|
||||
}
|
||||
]
|
||||
},
|
||||
"spacing": {
|
||||
"units": ["px", "rem", "%"]
|
||||
},
|
||||
"layout": {
|
||||
"contentSize": "800px",
|
||||
"wideSize": "1200px"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### 7.2 Customizer Options (if needed)
|
||||
|
||||
- Logo upload
|
||||
- Contact information (phone, email, address)
|
||||
- Social media links
|
||||
- Footer text
|
||||
- Google Analytics ID
|
||||
|
||||
---
|
||||
|
||||
## 8. Content Migration
|
||||
|
||||
### 8.1 From Existing Site
|
||||
|
||||
Content to migrate from homeprozrealestate.com:
|
||||
- [ ] Logo image
|
||||
- [ ] Team member photos and bios
|
||||
- [ ] Property photos (if available)
|
||||
- [ ] Testimonial text
|
||||
- [ ] Company description/mission
|
||||
- [ ] Contact information
|
||||
|
||||
### 8.2 Content Client Must Provide
|
||||
|
||||
- [ ] High-resolution logo (vector preferred)
|
||||
- [ ] Team headshots (professional quality)
|
||||
- [ ] Property listings data
|
||||
- [ ] Property photos
|
||||
- [ ] Written content for About page
|
||||
- [ ] Testimonials with permissions
|
||||
|
||||
---
|
||||
|
||||
## 9. Testing Checklist
|
||||
|
||||
### 9.1 Functionality
|
||||
- [ ] All pages load without errors
|
||||
- [ ] Navigation works (desktop and mobile)
|
||||
- [ ] Property archive displays correctly
|
||||
- [ ] Property filters work
|
||||
- [ ] Single property page displays all fields
|
||||
- [ ] Contact forms submit and send emails
|
||||
- [ ] Search returns relevant results
|
||||
- [ ] 404 page displays for invalid URLs
|
||||
- [ ] Links to external sites work (new tab)
|
||||
|
||||
### 9.2 Responsiveness
|
||||
- [ ] Mobile (320px - 767px)
|
||||
- [ ] Tablet (768px - 1023px)
|
||||
- [ ] Desktop (1024px+)
|
||||
- [ ] Large screens (1440px+)
|
||||
|
||||
### 9.3 Browser Compatibility
|
||||
- [ ] Chrome (latest)
|
||||
- [ ] Firefox (latest)
|
||||
- [ ] Safari (latest)
|
||||
- [ ] Edge (latest)
|
||||
- [ ] iOS Safari
|
||||
- [ ] Android Chrome
|
||||
|
||||
### 9.4 Performance
|
||||
- [ ] Lighthouse Performance score > 90
|
||||
- [ ] Images optimized
|
||||
- [ ] Caching enabled
|
||||
- [ ] No render-blocking resources
|
||||
- [ ] Core Web Vitals pass
|
||||
|
||||
### 9.5 SEO
|
||||
- [ ] All pages have unique titles
|
||||
- [ ] Meta descriptions set
|
||||
- [ ] Schema markup validates
|
||||
- [ ] XML sitemap generated
|
||||
- [ ] robots.txt configured
|
||||
- [ ] Canonical URLs set
|
||||
|
||||
---
|
||||
|
||||
## 10. Documentation Deliverables
|
||||
|
||||
### 10.1 User Documentation
|
||||
- Adding/editing properties guide
|
||||
- Managing property photos
|
||||
- Updating team information
|
||||
- Using the contact form
|
||||
- Basic WordPress admin guide
|
||||
|
||||
### 10.2 Developer Documentation
|
||||
- Theme structure overview
|
||||
- ACF field reference
|
||||
- Custom functions reference
|
||||
- Deployment notes
|
||||
|
||||
---
|
||||
|
||||
## 11. Post-Launch Support
|
||||
|
||||
### 11.1 Included in Warranty (60 days)
|
||||
- Bug fixes for custom code
|
||||
- Functionality not working as designed
|
||||
- Critical issues
|
||||
|
||||
### 11.2 Not Included (quoted separately)
|
||||
- New features
|
||||
- Design changes
|
||||
- Third-party plugin issues
|
||||
- Content updates
|
||||
- Training beyond initial session
|
||||
|
||||
### 11.3 Ongoing Hosting Support (2 hrs/month)
|
||||
- WordPress core updates
|
||||
- Plugin updates
|
||||
- Security monitoring
|
||||
- Backup verification
|
||||
- Minor content assistance
|
||||
|
||||
---
|
||||
|
||||
## 12. Risk Mitigation
|
||||
|
||||
| Risk | Mitigation |
|
||||
|------|------------|
|
||||
| ACF Pro license expiration | Included in hosting; developer manages renewal |
|
||||
| Plugin conflicts | Minimal plugin approach; test thoroughly |
|
||||
| Performance issues | Build lightweight; optimize images; use caching |
|
||||
| Content delays | Clear client responsibilities; content deadline |
|
||||
| Scope creep | Defined deliverables; change order process |
|
||||
| Browser compatibility | Test on all major browsers before launch |
|
||||
|
||||
---
|
||||
|
||||
## 13. Timeline Summary
|
||||
|
||||
| Phase | Duration | Deliverable |
|
||||
|-------|----------|-------------|
|
||||
| 1. Foundation | 2 days | Theme framework |
|
||||
| 2. Property System | 2 days | Property CPT + templates |
|
||||
| 3. Page Templates | 2 days | All page templates |
|
||||
| 4. Block Patterns | 1 day | Reusable patterns |
|
||||
| 5. Content & SEO | 0.5 day | SEO setup + content |
|
||||
| 6. Performance | 0.5 day | Optimized site |
|
||||
| 7. Testing & Training | 1 day | Launch-ready |
|
||||
| **Total** | **~8-9 days** | **Complete website** |
|
||||
|
||||
*Note: Actual calendar time may vary based on client feedback cycles.*
|
||||
|
||||
---
|
||||
|
||||
## 14. Open Questions / Decisions Needed
|
||||
|
||||
1. **Agent Management:** Use ACF options page or separate Agent CPT?
|
||||
2. **Testimonials:** Static content or Testimonial CPT for easy management?
|
||||
3. **Maps:** Google Maps embed or full API integration?
|
||||
4. **Property Images:** Max file size / dimensions requirements?
|
||||
5. **Email Notifications:** Which email(s) receive form submissions?
|
||||
|
||||
---
|
||||
|
||||
## 15. Approval
|
||||
|
||||
This implementation plan is a draft for review. Please confirm:
|
||||
- Technology stack is acceptable
|
||||
- Phase breakdown makes sense
|
||||
- All required features are covered
|
||||
- Any adjustments needed
|
||||
|
||||
---
|
||||
|
||||
*Document Version: 1.0*
|
||||
*Date: November 28, 2025*
|
||||
*Prepared by: Hanson.xyz Development Team*
|
||||
File diff suppressed because it is too large
Load Diff
Binary file not shown.
|
After Width: | Height: | Size: 2.0 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 429 KiB |
File diff suppressed because one or more lines are too long
@@ -0,0 +1,62 @@
|
||||
LANDPROZ CONTRACT REFERENCE EXAMPLES
|
||||
=====================================
|
||||
|
||||
This directory contains text extractions from Landproz project contracts to use as reference
|
||||
when building the HomeProz WordPress website contract.
|
||||
|
||||
DOCUMENTS INCLUDED:
|
||||
-------------------
|
||||
|
||||
1. landproz-ace-terms-of-service.txt
|
||||
- Final terms of service for the AuctionCast platform
|
||||
- Most comprehensive legal document from the Auctioncast project
|
||||
- Includes: acceptance of terms, privacy policy, data collection, user verification,
|
||||
access controls, payment terms, liability, intellectual property, termination clauses
|
||||
- Good reference for: comprehensive ToS structure, legal language, user obligations
|
||||
|
||||
2. landproz-project-proposal-2023.txt
|
||||
- Original project proposal for the live stream and bidding system (12-15-2022)
|
||||
- Flat fee project: $36,000 for 180 hours over 3 months
|
||||
- Includes: executive summary, objectives, implementation details
|
||||
- Good reference for: project proposal structure, objectives writing, high-level scope
|
||||
|
||||
3. landproz-statement-of-work-2023.txt
|
||||
- Statement of work for the bidding system project
|
||||
- Companion document to the project proposal
|
||||
- Includes: scope of work breakdown, design deliverables, development deliverables
|
||||
- Good reference for: SOW structure, defining deliverables clearly
|
||||
|
||||
4. landproz-whitelabel-proposal-2025.txt
|
||||
- More recent proposal for white-label Auctioncast site (5/27/2025)
|
||||
- WordPress-focused project with feature customization
|
||||
- Includes: detailed feature list, customer portal specifications, pricing structure
|
||||
- Good reference for: WordPress project scoping, feature specifications, deliverables list
|
||||
|
||||
5. landproz-compiled-promises-2023.txt
|
||||
- Document compiling all promises made during contract negotiation
|
||||
- Tracks commitments made outside the main contract
|
||||
- Good reference for: change management, promise tracking methodology
|
||||
|
||||
6. landproz-deliverables-review-2023.txt
|
||||
- Review document for tracking deliverable completion
|
||||
- Good reference for: project milestone tracking, acceptance criteria
|
||||
|
||||
USAGE NOTES:
|
||||
------------
|
||||
|
||||
These documents represent different contract types and stages:
|
||||
- Proposals (documents 2 and 4): How to pitch and scope projects
|
||||
- Statement of Work (document 3): How to define technical deliverables
|
||||
- Terms of Service (document 1): How to establish legal framework and user obligations
|
||||
- Project tracking (documents 5 and 6): How to manage scope and deliverables
|
||||
|
||||
For the HomeProz WordPress website contract, consider which elements are most relevant:
|
||||
- Is this a fixed-fee or hourly project?
|
||||
- What level of legal protection is needed?
|
||||
- How detailed should the deliverables list be?
|
||||
- What are the acceptance criteria?
|
||||
- What are the payment terms?
|
||||
- What is excluded from scope?
|
||||
|
||||
EXTRACTED: October 29, 2025
|
||||
SOURCE: Clients/Landproz/LP - Contracts - Agreements/
|
||||
+114
@@ -0,0 +1,114 @@
|
||||
Terms of Service for the AuctionCast Online Auction Platform
|
||||
1. Acceptance of Terms By using our online real estate auction service, you agree to comply with and be bound by these Terms of Service (TOS). Please read these terms carefully. If you do not agree to these terms, you shall not use this service. This agreement is between you and LANDPROZ Real Estate LLC (DBA AuctionCast) and you are required to agree to all portions of this Terms of Service to use our system.
|
||||
2. Privacy Policy
|
||||
Data Collection: We collect various types of data about users and their use of our site, including but not limited to personal identification information, bidding history, and site interaction patterns.
|
||||
Recordkeeping: All actions within our system are recorded. This is necessary for recordkeeping purposes and allows for audits of sales as required.
|
||||
Data Collection Techniques: We employ various techniques for data collection to enhance user experience and ensure regulatory compliance.
|
||||
Use of Cookies: In addition to the data collection methods previously described, our service utilizes "cookies" – files placed on your device – to enhance user experience. Cookies help us understand user preferences based on previous or current site activity, enabling us to provide improved services. We also use cookies to compile aggregate data about site traffic and site interactions.
|
||||
Third-Party Cookies: In some cases, we may also use cookies provided by trusted third parties. These may include analytics cookies that allow us to track and understand how you use our site, which helps us to improve our services and your user experience.
|
||||
3. Accuracy of Information and Verification
|
||||
Provision of Accurate Information: All users must provide accurate, complete, and current information as requested during registration and bidding processes. This includes, but is not limited to, your legal name, address, phone number, and financial information. Providing false, misleading, or incomplete information is a breach of these Terms of Service and may result in immediate termination of your account and access to our services.
|
||||
Verification Process: To ensure the integrity of our auctions, we may contact bidders by phone or other means to verify the information provided. This verification process is crucial to maintaining a secure and fair bidding environment.
|
||||
Bidding Approval: Approval to bid in an auction is granted on a per-auction basis and is not automatic. Users must apply for bidding approval for each auction in which they wish to participate. To ensure sufficient time for the verification process, we request that users sign up at least 5 days in advance of the auction. Late registrations may not be approved in time for participation in the auction.
|
||||
Consequences of Inaccurate Information: If at any point it is determined that a user has provided inaccurate or misleading information, we reserve the right to take appropriate actions, including but not limited to disqualification from current and future auctions, termination of the account, and legal action where necessary.
|
||||
User Cooperation: Users are expected to cooperate fully with any verification inquiries or requests for additional information. Failure to comply with these requests may result in the denial of bidding privileges.
|
||||
4. Access to Individual Auctions
|
||||
Determination of Access: Access to individual auctions on our platform is determined by our auction staff. This includes auction managers, brokers, agents, and other authorized personnel. The decision to grant or deny access to any auction is at their sole discretion.
|
||||
Criteria for Access: The criteria for allowing access to a particular auction may vary and are determined by the specific requirements of each auction. These criteria may include, but are not limited to, financial qualifications, compliance with previous auction rules, and the nature of the property being auctioned.
|
||||
Denial or Removal of Access: Auction staff reserve the right to deny or remove access to any auction at any time. This action can be taken for reasons including, but not limited to, failure to comply with auction rules, providing inaccurate information, disruptive behavior, or any other reason deemed sufficient by the auction staff.
|
||||
Notice of Decision: While we endeavor to notify users promptly of any decision regarding their access to an auction, there may be instances where immediate action is necessary without prior notice.
|
||||
Appeal Process: Users may request a review of a decision to deny or remove access by contacting our customer support. However, the initial decision will remain in effect until the review process is complete.
|
||||
User Responsibility: Users are responsible for ensuring they meet all the criteria for participation in an auction and for adhering to any instructions or guidelines provided by auction staff. Failure to do so may result in denial of access to current and future auctions.
|
||||
Changes to Access Policy: We reserve the right to modify the criteria and process for auction access at any time. Any changes will be communicated through updates to these Terms of Service or through direct communication with users where applicable.
|
||||
5. Binding Nature of Winning Bids
|
||||
Legally Binding Bids: All winning bids made through our platform are legally binding. By placing a bid, you are making a contractual commitment to purchase the listed property at price indicated in your bid if you are the winning bidder.
|
||||
Enforcement of Payment: In the event of a winning bid, we reserve the right to use any lawful means necessary to secure the purchase price from the user. This may include, but is not limited to, charging any registered payment methods, initiating legal proceedings, and employing collection agencies.
|
||||
User Responsibility: It is the user's responsibility to ensure that they have sufficient funds available to cover the total cost of any bid they place. Placing a bid without the intention or ability to fulfill the payment obligation is strictly prohibited and may result in legal action and permanent suspension from our platform.
|
||||
Payment Terms: Specific payment terms, including deadlines, acceptable payment methods, and any related fees, will be communicated to the winning bidder following the close of the auction.
|
||||
Consequences of Non-Payment: Failure to promptly fulfill the payment obligations of a winning bid may result in legal action, additional charges, and the forfeiture of the right to purchase the property. Delinquent payments will be additionally charged interest at the rate of the lesser of 18% per annum or the maximum amount allowable by law. Furthermore, non-payment may affect the user's ability to participate in future auctions.
|
||||
Attorney Fees: In the event that we must initiate legal action against you to enforce your payment obligations under this Section 5, you agree to pay our reasonable attorney fees, court costs, and other costs, expenses, and damages.
|
||||
6. Accuracy of Online Experience
|
||||
Portions of the online experience, especially those managed by auctioneers or staff, such as countdowns and timers, may not always be accurate. We endeavor to maintain precision but cannot guarantee the timeliness of these actions.
|
||||
Tie bids, bids in which more than one person places the same value bid, will be resolved such that the first bidder to place that value bid as seen by the bidding system, auctioneer, or clerks, will have their bid advanced. Tie bidders who are not first to bid the tie value are encouraged to bid again at a higher value to advance a new bid.
|
||||
7. Data Storage and Security
|
||||
Commitment to Security: We are committed to ensuring the security of user data. We take all reasonable precautions to safeguard the information collected through our platform, employing a variety of technical and organizational measures designed to protect data against unauthorized access, alteration, disclosure, or destruction.
|
||||
Data Retention: Data is retained in compliance with the regulatory requirements of the state and country in which the auction takes place, as well as the jurisdiction in which our company is registered. This includes adherence to any applicable real estate and data protection laws.
|
||||
Compliance with GDPR: In cases where any auction or user is based in a country governed by the General Data Protection Regulation (GDPR), we will adhere to the stringent data protection and privacy standards set by the GDPR.
|
||||
Use of Data: We do not sell user data to external entities. However, user data may be accessed and used by our contractors, assignees, service providers, and other parties involved in the operation and maintenance of our services. This use is limited to purposes necessary for the provision of our services and is governed by strict confidentiality agreements.
|
||||
Rights to Media Content: We do not assert any ownership or rights claims over media content provided to us by third parties. We assume that all media uploaded to our platform is done so with the rightful permission of the owner. The responsibility for securing appropriate rights and permissions for any media used on our site rests with the uploader.
|
||||
Responsibility and Liability: While we strive to maintain the highest standards of data security, we cannot guarantee the absolute security of user data. In the unlikely event of a data breach, we will take appropriate measures to mitigate any potential harm and will communicate with affected users in accordance with legal requirements and best practices.
|
||||
8. Cross-System Integration and Data Sharing
|
||||
Integration with External Platforms: Our service may offer integration with external systems and platforms, such as Google Sign-In or Facebook, to streamline user experience and facilitate easy access. Utilizing these integrations is optional and provided for user convenience.
|
||||
Sharing of Information: In cases where users choose to utilize these integrations, sharing of certain information between our platform and the external systems is necessary to enable these functionalities. This may include basic profile information, email address, and other data required for authentication and account synchronization.
|
||||
Limitation of Data Sharing: We are committed to ensuring that the sharing of data with external platforms is limited strictly to what is necessary for the integration to function effectively. We do not share any additional information beyond what is required for the purpose of these integrations.
|
||||
User Consent: By opting to use these integrated services, users provide their consent for the necessary data exchange between our platform and the external system. Users are encouraged to review the privacy policies of these external platforms to understand how their data is managed.
|
||||
Data Security in Integrations: We take measures to ensure that data shared with external platforms is transmitted securely. However, the security and privacy practices of these external platforms are outside our control, and we encourage users to exercise caution and discretion when enabling these integrations.
|
||||
Revocation of Access: Users have the option to revoke our access to their data on external platforms at any time through their settings on the respective platforms. Revoking access may affect the functionality of the integration on our service.
|
||||
9. Client Access Hardware and Liability
|
||||
Requirement of Client Hardware: Access and use of our service require client hardware, such as a computer or mobile device, with adequate capabilities to support online bidding activities. Users are responsible for ensuring that their hardware meets the necessary technical specifications for effective use of our service.
|
||||
Hardware and Connectivity Issues: We are not liable for any failures, malfunctions, or inadequacies of client hardware or internet access. This includes, but is not limited to, hardware crashes, slow or unstable internet connections, and compatibility issues. It is the user’s responsibility to maintain and ensure the proper functioning of their equipment and internet connection.
|
||||
Impact of Hardware Failure: In the event of hardware or connectivity issues on the user’s side, we are not responsible for any resulting inability to place bids, delayed bidding, or any unintended outcomes such as unintentionally winning an auction. Users must ensure a stable and reliable connection and hardware setup when participating in auctions.
|
||||
Recommendations for Bidders: To minimize the risk of hardware or connectivity issues, we recommend that users:
|
||||
Test their hardware and internet connection prior to participating in an auction.
|
||||
Have a backup plan, such as an alternative device or internet connection, in case of unforeseen issues.
|
||||
Familiarize themselves with the auction platform’s functionality well in advance of the auction.
|
||||
No Liability for Technical Issues: We do not accept liability for any loss, damage, or inconvenience caused by user-side technical failures. This includes issues with bidding, viewing, or participating in auctions due to such failures.
|
||||
User Acknowledgement: By using our service, users acknowledge and agree that they are aware of the risks associated with online bidding, including potential hardware and internet connectivity issues, and agree to hold us harmless for any related difficulties or losses.
|
||||
10. Termination of Service We reserve the right to terminate your access to the service at any time, for any reason, including but not limited to the provision of false information. Termination may be without prior notice, and we may immediately deactivate or delete your account and all related information and files.
|
||||
11. Indemnification Users agree to indemnify and hold harmless our service, its affiliates, officers, agents, employees, and partners from any claim or demand made by any third party due to or arising out of your actions, your use of the service, your connection to the service, your violation of the TOS, or your violation of any rights of another.
|
||||
12. Changes to Terms of Service We reserve the right to modify these TOS at any time without prior notice. Your continued use of the service following the posting of any changes to these TOS constitutes acceptance of those changes.
|
||||
13. Governing Law and Venue These terms will be governed by and construed in accordance with the laws of the State of Minnesota, without giving effect to any principles of conflicts of law. The exclusive venue for any dispute arising out of these Terms of Service shall be the state or federal courts encompassing Freeborn County, Minnesota.
|
||||
14. Agreement to Terms By using our service, you signify your agreement to these Terms of Service. If you do not agree to these terms, please do not use our service.
|
||||
|
||||
CALIFORNIA ADDENDUM:
|
||||
15. Additional Information for California Residents. Under California law, specific disclosures are required, and California residents have additional rights regarding their personal information. Please review this section to learn more.
|
||||
|
||||
Your California Consumer Privacy Act of 2018 (CCPA) Rights
|
||||
|
||||
Categories of Personal Information We Collect
|
||||
|
||||
The California Consumer Privacy Act of 2018, as amended from time to time (“CCPA”) requires specific disclosures for each category of personal information that we collect. As more fully described in Sections B, C and D of this Privacy Notice, we may collect, use, or share the following categories of personal information:
|
||||
|
||||
Identifiers (§1798.140 (o)(1)(A) and (B)) which include elements such as: (i) contact information (e.g., name, mailing address, email address, phone number); and (ii) online identifiers (e.g., Internet protocol (IP) address, account numbers, device identifiers such as mobile advertising IDs);
|
||||
Demographics (§1798.140 (o)(1)(C)) which include elements such as age and gender;
|
||||
Personal Information under subdivision (e) of Section 1798.80 of the California Civil Code (§1798.140 (o)(1)(B)) which includes payment information (e.g., payment card number, expiration date and billing information);
|
||||
Commercial Information (§1798.140 (o)(1)(D)) which include elements such as: transactional information (e.g., activity, listings or bids, requests);
|
||||
Internet or other electronic network activity (§1798.140 (o)(1)(F)) which include elements such as information about how you use, access, or interact with the Digital Services such as comments, photos, videos and other content you choose to publish on the Digital Services, information about your device, browser or operating system);
|
||||
Geolocation Data (§1798.140 (o)(1)(G)) which include elements such as location information (e.g., city and state, or precise location information if location services are active on your device);
|
||||
Audio, Electronic, Visual, Thermal, Olfactory or Similar Information (§1798.140 (o)(1)(H)) which include elements such as recordings of your calls with our call center;
|
||||
Professional or Employment-Related Information (§1798.140 (o)(1)(I)) which include elements such as your professional email address, phone number or other contact information if you have used such professional or employment related personal information to make a listing, place a bid, register for an account or to receive communications; and
|
||||
Inferences (§1798.140 (o)(1)(K)) which include elements such as inferences regarding your preferences or other characteristics (e.g., cooking enthusiast, travel, food and dining).
|
||||
|
||||
Your California Consumer Privacy Act of 2018 (CCPA) Privacy Rights
|
||||
|
||||
Residents of California may have the following rights:
|
||||
|
||||
1. Right to know and access your personal information. Under CCPA, you have the right to:
|
||||
Know the categories of personal information we collect and the categories of sources from which we got the information;
|
||||
Know the business or commercial purposes for which we collect and share personal information;
|
||||
Know the categories of third parties and other entities with whom we share personal information; and
|
||||
Access the specific pieces of personal information we have collected about you.
|
||||
|
||||
2. Right to deletion. In some circumstances (subject to certain exceptions), you may ask us to delete your personal information. These exceptions may include pending payments, active bids, or other incomplete transactions connected to your account.
|
||||
|
||||
3. Right to opt out of sales. We may share your personal information with third parties in ways that may constitute a “sale” under CCPA. You may request that we not “sell” your personal information on a going forward basis.
|
||||
|
||||
If you choose to use the Digital Services to interact with Sellers and third parties, including if you successfully win a bid or complete a transaction with another user or third party that may be integrated with the Digital Services, we will provide the other user or third party, as appropriate, with your personal information to facilitate the transaction you requested (including, your name and contact information). This type of sharing does not constitute a “sale” of your personal information by us as it is done at your direction. If you reengage with us after opting out of the “sale” of your personal information, such as by submitting a bid, signing up for a newsletter and/or entering a sweepstakes or contest you acknowledge that your personal information may be used and shared in accordance with this Privacy Notice.
|
||||
|
||||
4. Right to be free from discrimination. You may exercise any of the above rights without fear of being discriminated against. We are permitted to provide a different price or rate to you if the difference is directly related to the value provided to you by your data.
|
||||
|
||||
We use the information you provide to make your CCPA rights requests to verify your identity, locate the personal information we may hold about you and act upon your request. We strongly recommend that you submit the email and postal address that you used when you created accounts, listed or placed a bid on a listed vehicle or other products and services, or signed up for a newsletter. After you submit a CCPA rights requests, we may ask you to verify your identity and/or access to the email address you submitted. You are required to verify your identity and/or email in order for us to proceed with your CCPA rights requests. Please check your spam or junk folder in case you can’t see the verification email in your inbox.
|
||||
|
||||
Authorized Agents
|
||||
|
||||
For any of the CCPA rights, you may designate an authorized agent to make a request on your behalf. In the request, you or your authorized agent must provide information sufficient for us to verify the identity of your agent and that your agent has been properly authorized to act on your behalf; this may take additional time to fulfill your request. If you are an authorized agent working on behalf of a consumer, you will need to fill out the relevant CCPA request form listed above on behalf of the consumer with the consumer’s information.
|
||||
|
||||
Minors
|
||||
|
||||
We do not knowingly collect or disclose personal information of minors under the age of 16, without affirmative authorization.
|
||||
|
||||
Your Shine the Light California Rights (CA Civil Code § 1798.83)
|
||||
|
||||
You may also have the right to request a list of third parties to which certain personal information (as defined by California Civil Code § 1798.83) obtained through a Digital Service was disclosed by Luxury Auto Group Inc. during the preceding year for those third parties’ direct marketing purposes. If you are a California resident and want such a list, please contact us at PO Box 4351, Mankato MN 56002. For such request, you must put the statement “Your California Privacy Rights” in the body of your request, as well as your name, street address, city, state, and zip code. In your request, you need to attest to the fact that you are a California resident and provide a current California address for our response. Please also indicate in your request the name of the Digital Service to which your request applies. Please note that we will not accept requests via the telephone, email, or by facsimile, and we are not responsible for notices that are not labeled or sent properly, or that do not have complete information.
|
||||
|
||||
|
||||
+18
@@ -0,0 +1,18 @@
|
||||
Objectives
|
||||
Replace bidwrangler.com with custom functionality, removing the dependency on bidwrangler.com.
|
||||
Improve the auction website interface to simplify the experience of finding the currently active auction and live stream, and place bids.
|
||||
Add a chat component to the site, allowing end users to communicate to the Landproz staff through the website.
|
||||
Incomplete
|
||||
Replace the live stream component of the application with a custom implementation with better video fidelity and more reliable broadcasting.
|
||||
Configure the new pages to be tracked by existing analytics packages, and provide a page for Landproz staff to view real time viewership and conversion count information
|
||||
Incomplete
|
||||
Create administration pages for Landproz staff to manage the new functionality, and to view stream statistics.
|
||||
Provide this functionality in a custom solution, so that the end result is proprietary, and gives Landproz an edge over its competitors.
|
||||
|
||||
List of Features
|
||||
Accordion dropdowns for descriptions
|
||||
Analytics not just for bidders but how many people are just viewing
|
||||
Bidding History
|
||||
Countdown timer
|
||||
Single Sign on Google, Etc
|
||||
Mobile specific stuff
|
||||
+83
@@ -0,0 +1,83 @@
|
||||
Objectives
|
||||
Replace bidwrangler.com with custom functionality, removing the dependency on bidwrangler.com.
|
||||
Improve the auction website interface to simplify the experience of finding the currently active auction and live stream, and place bids.
|
||||
Add a chat component to the site, allowing end users to communicate to the Landproz staff through the website.
|
||||
Replace the live stream component of the application with a custom implementation with better video fidelity and more reliable broadcasting.
|
||||
Configure the new pages to be tracked by existing analytics packages, and provide a page for Landproz staff to view real time viewership and conversion count information
|
||||
Create administration pages for Landproz staff to manage the new functionality, and to view stream statistics.
|
||||
Provide this functionality in a custom solution, so that the end result is proprietary, and gives Landproz an edge over its competitors.
|
||||
|
||||
Implementation Details
|
||||
The current Landproz websites are written in the PHP language using the frameworks Wordpress and Laravel. We will update the source code for these two sites to include live streaming and bidding functionality right in the source code.
|
||||
Live Stream
|
||||
|
||||
We will update the live streaming functionality with an integration with Cloudflare Live Stream. Details of this service can be found at:
|
||||
|
||||
https://www.cloudflare.com/products/cloudflare-stream/
|
||||
|
||||
The result will be an integration into http://api.landproz.com/ for starting and monitoring the live stream. The stream itself will work with the RTMP protocol, used in popular broadcasting software such as OBSStudio.
|
||||
Frontend User Experience
|
||||
The website will be updated with a single page which displays the upcoming or currently active property being bid upon. The page will include the live stream, property details, bidding details, and allow users to register, bid, and chat with the site administrators.
|
||||
A link to this page will be featured prominently on the home page, with a preview of the auction live stream, allowing users to quickly navigate the site and bring them to the live auction page. This page will be easier to use then the existing bidwrangler interface, and improve it with elements designed to highlight the bids being placed, and make the overall auction experience more interesting.
|
||||
The new frontend functionality will be developed using responsive design, allowing the pages to be usable on both desktop and mobile devices. The new experience will also be developed to track provide real time viewership information to the Landproz staff, and where possible, integrate into existing Analytics on the site.
|
||||
Modifications to the front end experience will be implemented as a Wordpress plugin, to not interfere with other third party website work being performed in parallel, and to allow it to be ported to future website redesigns.
|
||||
Administration Panel
|
||||
The administration panel will be updated to have new fields for managing property listings, including when the auctions will be performed, and details about the type of auction and other relevant information.
|
||||
Additional grids will be created to allow the site administrators to create, view, edit, and delete bidding registrants and their bids.
|
||||
A dashboard for the administrator to review the current live stream and auction will be developed, presenting viewer statistics for the auction, as well as notifications of activities such as new users being registered, which users are viewing the auction, and any bids that are placed. The administrator will also be able to use this screen to submit floor bids.
|
||||
Auction Styles
|
||||
There are multiple styles of auctions Landproz performs in. During the design phase of the project, we will interview Landproz to collect details about the workflows of the multiple types of auctions performed, and incorporate those workflows into the developed software.
|
||||
CHOICE INCOMPLETE
|
||||
|
||||
Scope of Work
|
||||
The Developer will update the website Landproz.com, performing the following services for the Client (the "Services"):
|
||||
Design
|
||||
Design and client acceptance of the user and feature experience for the custom auction system, implementing the multiple styles of auctions performed by the Client.
|
||||
Production of wireframes for the frontend and admin pages for the custom auction system
|
||||
Development
|
||||
Frontend:
|
||||
Live stream replaced with a custom self hosted solution, supporting RTMP streaming, and broadcast using an integration with Cloudflare’s content delivery network
|
||||
Dedicated page for showcasing the stream, the current property, and to place bids on the currently live auction
|
||||
User registration, user management, and bidding (CRM functionality)
|
||||
Simple chat interface between the users and the auction staff
|
||||
Administration panel:
|
||||
A dashboard with the live stream status, viewer statistics, live bidding information, and user chat
|
||||
Modifications to the existing new and edit auction listing screens to allow for scheduling live auctions
|
||||
User and bid management information grids
|
||||
Testing and client acceptance of the live stream feature and updated auction system
|
||||
Feature documentation
|
||||
Project management
|
||||
MEETING 3-20
|
||||
Promises to Brian Haugen:
|
||||
|
||||
Set up the filtering in the platform as it was done once before.
|
||||
Dayna will lead the project management and will inform Brian about when and where meetings are supposed to be, as well as what he needs to review.
|
||||
Ensure that Brian Hanson and Luke are included in the project.
|
||||
Promises to Beau Jensen:
|
||||
|
||||
Create a new listing feature that turns into a pending feature, which can sit when it's not in use.
|
||||
The auction feature might be placed at the bottom of the auctions, but above the listings for ease of finding fresh ones.
|
||||
Implement keyword functionality similar to landwatch.com.
|
||||
Create filters in the platform.
|
||||
Follow a similar interface to landwatch.com for typing and testing the county, state, and city.
|
||||
The auctions will live at the top of the platform, and the users will be able to access the whole list.
|
||||
The platform will include a message board for back-and-forth communication between users and administrators. Individual messages will also be possible.
|
||||
Bids can be placed by users, and pre-bids are also possible.
|
||||
The platform will be similar to BidWrangler and will include a hyperlink that says "Click here to bid". The design will be branded and made to look better than BidWrangler.
|
||||
The software should be built to direct where you want it to populate. It will be the driver that you can hook to those individually and put it in the software one time.
|
||||
The backend will be created so that it can look like it does now with listings.
|
||||
Please note that these are the direct interpretations of the transcript. It's recommended to cross-verify these points with the actual meeting minutes or discussion context to ensure complete accuracy.
|
||||
MEETING 5-22
|
||||
Brian discussed the functionality of user registration, aiming to make it as simple as possible with options to log in via Google, Facebook, and Twitter (lines 1-2).
|
||||
Brian explained that the auction functionality was created as a separate WordPress plugin. This allows for minimal interaction between the AuctionCast functionality and the rest of the website. The system has been designed for potential reuse on other websites, though it will require additional work to set it up for multiple clients (lines 3-4).
|
||||
Brian requested clarification on bidding processes for auctions with multiple tracks, noting that BidWrangler didn't seem to have a specific workflow for this. He suggested that this process was primarily handled by the auctioneers on the clerking screen (lines 5-6).
|
||||
He stated that he anticipates having the workflow implemented within the next few days and would appreciate feedback (line 18).
|
||||
Brian offered to share a spreadsheet detailing the progress on various tasks and how much work is left on each of them (line 19).
|
||||
He discussed the concept of a parcel and how it works in the context of the auction system (lines 21-22).
|
||||
Brian shared that he expects to have all core functionalities ready for testing by the end of the next week. He mentioned that he will also provide a beta version for testing (lines 34-35).
|
||||
He discussed the potential use of notifications and text messages in the system, for instance, alerting users about new chats or updates (lines 37-38).
|
||||
Brian mentioned that he has been designing the website with a focus on mobile users, as they will likely constitute the majority of site visitors (line 40).
|
||||
He shared his intentions to add timers to the auction functionality, although he noted some potential challenges in synchronizing the timer with the video stream due to delays (lines 51-53).
|
||||
Brian concluded the meeting by expressing his anticipation to get the auction platform into the hands of the users and asked for a follow-up meeting in a week's time (line 57).
|
||||
|
||||
|
||||
+65
@@ -0,0 +1,65 @@
|
||||
Landproz.com Live Stream and Bidding System Update
|
||||
Project Proposal
|
||||
Prepared on 12-15-2022
|
||||
Executive Summary
|
||||
Landproz.com requires a custom implementation of the functionality currently provided to their website by the third party service Bidwrangler.com. This custom solution would include a page to view details about an auction in progress, a live video stream of the auction floor, and a simplified user experience for buyers to view the and place bids on properties being auctioned.
|
||||
The updated functionality will also include updates to the admin experience on http://api.landproz.com/ - merging all controls for setting up live auctions, registrants, and bids into the website http://api.landproz.com/.
|
||||
These updates will increase customer engagement, and allow for more detailed customization of the auction experience to be made in the future.
|
||||
The project is quoted at a flat fee of $36,000. $12,000 will be due at project acceptance. The project is estimated to take 180 hours to complete, over the course of 3 months from when the project is signed and approved.
|
||||
|
||||
Objectives
|
||||
Replace bidwrangler.com with custom functionality, removing the dependency on bidwrangler.com.
|
||||
Improve the auction website interface to simplify the experience of finding the currently active auction and live stream, and place bids.
|
||||
Add a chat component to the site, allowing end users to communicate to the Landproz staff through the website.
|
||||
Replace the live stream component of the application with a custom implementation with better video fidelity and more reliable broadcasting.
|
||||
Configure the new pages to be tracked by existing analytics packages, and provide a page for Landproz staff to view real time viewership and conversion count information
|
||||
Create administration pages for Landproz staff to manage the new functionality, and to view stream statistics.
|
||||
Provide this functionality in a custom solution, so that the end result is proprietary, and gives Landproz an edge over its competitors.
|
||||
|
||||
Implementation Details
|
||||
The current Landproz websites are written in the PHP language using the frameworks Wordpress and Laravel. We will update the source code for these two sites to include live streaming and bidding functionality right in the source code.
|
||||
Live Stream
|
||||
|
||||
We will update the live streaming functionality with an integration with Cloudflare Live Stream. Details of this service can be found at:
|
||||
|
||||
https://www.cloudflare.com/products/cloudflare-stream/
|
||||
|
||||
The result will be an integration into http://api.landproz.com/ for starting and monitoring the live stream. The stream itself will work with the RTMP protocol, used in popular broadcasting software such as OBSStudio.
|
||||
Frontend User Experience
|
||||
The website will be updated with a single page which displays the upcoming or currently active property being bid upon. The page will include the live stream, property details, bidding details, and allow users to register, bid, and chat with the site administrators.
|
||||
A link to this page will be featured prominently on the home page, with a preview of the auction live stream, allowing users to quickly navigate the site and bring them to the live auction page. This page will be easier to use then the existing bidwrangler interface, and improve it with elements designed to highlight the bids being placed, and make the overall auction experience more interesting.
|
||||
The new frontend functionality will be developed using responsive design, allowing the pages to be usable on both desktop and mobile devices. The new experience will also be developed to track provide real time viewership information to the Landproz staff, and where possible, integrate into existing Analytics on the site.
|
||||
Modifications to the front end experience will be implemented as a Wordpress plugin, to not interfere with other third party website work being performed in parallel, and to allow it to be ported to future website redesigns.
|
||||
Administration Panel
|
||||
The administration panel will be updated to have new fields for managing property listings, including when the auctions will be performed, and details about the type of auction and other relevant information.
|
||||
Additional grids will be created to allow the site administrators to create, view, edit, and delete bidding registrants and their bids.
|
||||
A dashboard for the administrator to review the current live stream and auction will be developed, presenting viewer statistics for the auction, as well as notifications of activities such as new users being registered, which users are viewing the auction, and any bids that are placed. The administrator will also be able to use this screen to submit floor bids.
|
||||
Auction Styles
|
||||
There are multiple styles of auctions Landproz performs in. During the design phase of the project, we will interview Landproz to collect details about the workflows of the multiple types of auctions performed, and incorporate those workflows into the developed software.
|
||||
|
||||
Project Phases
|
||||
The process for development of the new Landproz.com features will follow these phases:
|
||||
Design – Approx 30 hours / 3 weeks
|
||||
We will create simple mockups of new and updated pages on the site, incorporating fields and functionality from bidwrangler.com, as well as any customization to the functionality which is feasible to implement within the timeline of the project. This process will involve discussions with members of the Landproz team to gather information about specific requirements and workflows that Landproz engages in for the auctions.
|
||||
Landproz will review the wireframes and other design assets made during this phase of the project. Upon approval of the wireframes and designs, the project will continue to the development phase.
|
||||
Development – Approx 90 hours / 8 weeks
|
||||
We will methodically develop and build out the various screens and features of the site. As development progresses, we will provide updates as to our progress, and ask for feedback as appropriate. The updated site will be available on a temporary web URL for review during development.
|
||||
Testing and Acceptance – Approx 20 hours / 2 weeks
|
||||
Once development has completed, and internal quality assurance testing has completed, we will work with the Landproz team to demonstrate the new functionality and get feedback. We will fix issues with the new functionality until Landproz approves the changes.
|
||||
Launch and Warranty
|
||||
Finally, the website updates will be deployed to the production Landproz.com website. We will work with the web hosting company Webspec.com to incorporate the new changes into the website.
|
||||
After the conclusion of the project, we will guarantee our work for 60 days – any functionality which doesn’t work as it was designed to will be fixed, free of charge. Support after this period, or new functionality, will be separately quoted.
|
||||
|
||||
|
||||
Project Management
|
||||
In addition to the above estimates and timeline, we estimate that project management, quality assurance, communication, and other project overhead will take a total of 40 hours.
|
||||
As this is a “flat fee” project, the total number of hours the project will take to complete won’t factor into the end cost of the project. The estimates are provided for visibility as to the scope of the development effort of the project.
|
||||
|
||||
Conclusion
|
||||
We are excited to take on this project of adding new functionality to Landproz.com. We believe the implementation of the project will be a good experience for everyone involved. The resulting changes will be a strong improvement to the Landproz customer experience, and give Landproz the flexibility and foundation to continue to build out and expand future online business initiatives.
|
||||
We hope to build a strong business relationship with the success of this project. We are confident that the quality and results of the implementation will allow us to be a preferred partner for future custom development needs.
|
||||
If you are ready to start the project, please review the attached statement of work, and let us know if you have any questions!
|
||||
|
||||
Thank you for your consideration,
|
||||
Brian Hanson & the Hanson.xyz team
|
||||
|
||||
+46
@@ -0,0 +1,46 @@
|
||||
Landproz.com Live Stream and Bidding System Update
|
||||
Statement of Work
|
||||
Prepared on 12-15-2022
|
||||
Project Description
|
||||
This contract (the "Agreement") is made between Hansonxyz LLC (the "Developer"), and LandProz (the "Client").
|
||||
The Developer and the Client hereby agree as follows:
|
||||
The Developer will provide a custom solution to replace functionality currently provided by bidwrangler.com, on the clients website, Landproz.com. This will include an updated, custom solution for handling the auction video stream, and an updated interface for users to place bids on auctions. It will also include updates to backend administrative functionality to manage bidders, bids, and the live stream.
|
||||
Updates to the frontend website experience of Landproz.com will be developed using responsive design, and will be usable by mobile devices within a mobile web browser. The project excludes the development of a native mobile application, and other functionality provided by bidwrangler.com outside of the following “Scope of Work”.
|
||||
Scope of Work
|
||||
The Developer will update the website Landproz.com, performing the following services for the Client (the "Services"):
|
||||
Design
|
||||
Design and client acceptance of the user and feature experience for the custom auction system, implementing the multiple styles of auctions performed by the Client.
|
||||
Production of wireframes for the frontend and admin pages for the custom auction system
|
||||
Development
|
||||
Frontend:
|
||||
Live stream replaced with a custom self hosted solution, supporting RTMP streaming, and broadcast using an integration with Cloudflare’s content delivery network
|
||||
Dedicated page for showcasing the stream, the current property, and to place bids on the currently live auction
|
||||
User registration, user management, and bidding (CRM functionality)
|
||||
Simple chat interface between the users and the auction staff
|
||||
Administration panel:
|
||||
A dashboard with the live stream status, viewer statistics, live bidding information, and user chat
|
||||
Modifications to the existing new and edit auction listing screens to allow for scheduling live auctions
|
||||
User and bid management information grids
|
||||
Testing and client acceptance of the live stream feature and updated auction system
|
||||
Feature documentation
|
||||
Project management
|
||||
Cost and Payment
|
||||
In consideration for the Services, the Client will pay the Developer a total fee of $36,000. The payment schedule will be as follows:
|
||||
$12,000 upfront to commence the project
|
||||
The remaining $24,000 upon completion of the project
|
||||
Timeline for completion
|
||||
The project is expected to be completed within 3 months of the date of this Agreement. If unforeseen circumstances arise that prevent the Developer from completing the project within this timeline, the Developer will notify the Client in writing and the timeline for completion may be extended by mutual agreement of the parties.
|
||||
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. If the Developer chooses to perform the additional work and determines that it is feasible to do so, 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.
|
||||
Intellectual Property Rights and Deliverables
|
||||
Upon completion of the project, and full payment by the Client, the Developer will transfer all rights, title, and interest in and to the custom auction system and all related materials, including but not limited to source code, design documents, and wireframes (the "Deliverables"), to the Client. The Developer will also provide the Client with a perpetual, non-exclusive license to use, reproduce, modify, and distribute the custom auction system and related materials for any purpose.
|
||||
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 contract.
|
||||
Governing Law and Venue
|
||||
This contract will be governed by and construed in accordance with the laws of the State of Minnesota, without giving effect to any principles of conflicts of law. Any legal action arising out of or relating to this contract shall be filed only in the state or federal courts located in Minnesota, and the parties hereby consent to the personal jurisdiction of such courts.
|
||||
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.
|
||||
|
||||
IN WITNESS WHEREOF, the parties have executed this Agreement:.
|
||||
|
||||
|
||||
+103
@@ -0,0 +1,103 @@
|
||||
Auctioncast.com ‘White Label’ Site Proposal
|
||||
Prepared by Brian Hanson (HansonXyz LLC) for Landproz on 5/27/2025
|
||||
|
||||
HansonXyz will produce for Landproz a new WordPress site which features similar functionality to landproz.com, but with new branding, new content, and an implementation of the ACE Auctioncast experience currently used on Landproz.com. The auction experience will be functionally the same, only with different colors, and different branding.
|
||||
|
||||
Features to be Added / Project Deliverables
|
||||
There will be a global login at the top of the Auctioncast website which lets the user of the website login as either a registrant or an ACE backend user. From the end user’s perspective, these accounts will start to seem unified, as if they only have one account, their ‘Auctioncast’ account.
|
||||
ACE users who are not Auctioncast staff will get a new customer portal upon logging in. In this customer portal, there will be:
|
||||
The customer’s logo
|
||||
A list of auctions which the user is assigned to as an ‘Auction Manager’
|
||||
The user can click on an auction to see the auction’s details, including:
|
||||
Description
|
||||
Items
|
||||
Images
|
||||
Registrants on the auction w/ contact details
|
||||
Current bidding status (or who won each auction)
|
||||
Basic Analytics
|
||||
Chat messages from registrants
|
||||
A link to the ‘public’ display for an auction
|
||||
A link to the ‘auctioneer’ display for an auction
|
||||
Note: All of these screens will be read-only. The Auctioncast staff will handle entering in all auction details. The bidding status screens will be similar to the read-only clerk interface, allowing only for interaction to chat messages
|
||||
The users will be able to add registrants to their auctions, and send messages to registrants, in much the same way auction managers are able to right now in the current ACE system
|
||||
For each new auction entered by a landproz clerk, an interactive onboarding checklist feature will be added and visible on the client portal, with details of what is requested of the client for each auction to be finalized later. Some of these details may be – Location, deeded acres, images, description, sales te0rms, etc. Forms will be added to accept each piece of provided information, and the clerk will be able to review these submissions and either approve or provide feedback, which will also generate email notifications to the client appropriate for this feature.
|
||||
The user will be able to upload documents in the customer portal for the Auctioncast staff to use, using a drag and drop interface to upload files to their file manager. The Auctioncast staff will create ‘requests for documents’ which will show up on the dashboard as an item which can be clicked on, and then users will be able to upload documents and add comments to the request section.
|
||||
All other ACE functionality and non customer data will be hidden.
|
||||
|
||||
As part of this project, the following ACE features will also be implemented:
|
||||
Chat conversations by read-only users will not affect a chat’s ‘viewed’ status.
|
||||
Chat conversations will show who ‘read’ a conversation in the clerk UI.
|
||||
Chat conversations will show when someone is ‘typing’.
|
||||
Multi tenant support (multiple B2B customer support) will be added to ACE, and Landproz will become a tenant.
|
||||
Auctions will be able to be performed on either the Auctioncast website or the Landproz website.
|
||||
The new Auctioncast website will have a page specifically for partners, to show the partners logo, contact information, and upcoming and past auctions. This partner page will be accessible by subdomain (for example, https://iowalandbroker.auctioncast.com/ .
|
||||
The Auctioncast Wordpress plugin will be improved to make it able to work simultaneously on landproz.com and auctioncast.com.
|
||||
ACE backend will be improved to have better mobile device compatibility.
|
||||
Updated permissions scheme pending the discussion of what those permissions entail with Dayna
|
||||
The incomplete development tasks assigned in Trello in May 2025 related to the white label website features will be completed, including:
|
||||
Header bar sign in
|
||||
Countdown clock
|
||||
‘My Auctions’
|
||||
|
||||
Timeline for Completion and Budget:
|
||||
This project is estimated to take 60 development hours to complete, and is sold at a discounted rate of $175 per hour, for a total fixed bid cost of $10,500 for the entire project. This will include:
|
||||
Frontend Development – theming cloned Auctioncast site
|
||||
Backend Development – ACE login / client administration panel features
|
||||
Testing & client feedback
|
||||
Deployment
|
||||
Final testing and delivery
|
||||
The timeline for this project will be aggressive. Development will take place over 3 weeks, starting on May 28th and concluding on June 18th. Major milestones include:
|
||||
Thursday June 5th – progress demonstration and client feedback meeting
|
||||
Thursday June 12th – progress demonstration and client feedback meeting
|
||||
Thursday June 19th – final demonstration of features of software
|
||||
Friday June 20th – meeting on testing plan
|
||||
Week of June 23rd – June 27th – testing, bugfixes, and final product approval
|
||||
July 1st – Deployment to live Auctioncast.com website. The project will be invoiced at this time.
|
||||
July 1st – 15th – no activity, this is reserved for team training, and additional last minute change requests. Fixes to features promised as part of delivery will be in scope, other feature requests will be billed as additional work at the developer’s normal hourly rate of $250 per hour.
|
||||
|
||||
Change Requests
|
||||
Due to the tight timeline and budget of this project, additional out of scope features outside of the scope defined in this document will be discouraged. Changes to scope will require discussion, a quote, and approval by both the client and developer in writing to proceed.
|
||||
HansonXyz will recommend the client wait until after delivery of the final product on July 1st to add additional features.
|
||||
|
||||
Considerations
|
||||
The new Auctioncast website will have little to no change in site content from the source Landproz website outside of changes in font, colors, and brand name. In particular, the front page of the site will need to be redesigned. It will be the responsibility of the client to provide:
|
||||
Updated color scheme preferences
|
||||
Content for each page of the site they wish to display
|
||||
Any imagery or other marketing material they wish to show on the site.
|
||||
Pages that are not relevant on Auctioncast.com, such as the ‘meet the team’ page, will be removed.
|
||||
Additional content and feature changes to the Auctioncast site will be quoted and billed separately, either as a separate project, or future ongoing maintenance.
|
||||
|
||||
Contract Legal Matters
|
||||
Independent Contractor Status
|
||||
HansonXyz 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.
|
||||
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.
|
||||
Delivery Timeline
|
||||
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.
|
||||
Payment Terms
|
||||
The project will be invoiced in full upon delivery to the live Auctioncast.com website on July 1st, 2025, with net 30 payment terms.
|
||||
Intellectual Property and Work Product
|
||||
All right, title and interest, including copyright and other intellectual property rights in and to any data, information, ideas, concepts or material provided by Company to Consultant for use in performing Services are and shall remain Company’ property (“Company Content”). Company grants Consultant a non-exclusive, non-transferable license during the Term to reproduce, display and perform Company Content solely in connection with, and solely as required for, the performance of the Services. Company Content shall be considered Confidential Information of Company.
|
||||
As between the parties, Consultant agrees that Company is the sole and exclusive owner of all inventions, improvements, computer programs, discoveries, ideas, processes, systems, writings or other works authored, developed, discovered, or conceived by Consultant, solely or jointly with others, that (a) are produced as part of, or in the course of performing, the Services; or (b) are authored, developed, discovered, or conceived during the term of this Agreement with the use or partial use of Company’s systems, equipment, supplies, materials, facilities, computer
|
||||
programs, or Confidential Information (collectively, “Work Product”). Consultant agrees to assign, and hereby assigns, to Company all rights, title and interest it may have in or to the Work Product, including without limitation all patent rights, trademark rights, copyrights, trade secret rights, and other intellectual property or proprietary rights therein. Consultant shall render all reasonably required assistance to Company to effect the foregoing assignment and protect the rights described above. Consultant warrants it has all right, power and authority to effect all assignments, transfers and waivers provided herein. To the extent any pre-existing materials, such as information or code, owned by Consultant (“Consultant Materials”) are embedded or incorporated in, or necessary for use of the Work Product, Consultant hereby grants Company a non-exclusive, fully-transferable and sublicensable, royalty-free, worldwide, perpetual right and license to copy, use, perform, publicly display, and prepare derivative works of the Consultant Materials in connection with such Work Product.
|
||||
Consultant shall retain all ownership rights in and to any pre-existing materials, libraries, tools, utilities, frameworks, or code developed independently of the Services (collectively, "Consultant Tools"), even if such Consultant Tools are incorporated into the Work Product. To the extent any Consultant Tools are included in the Work Product, Consultant hereby grants Company a non-exclusive, royalty-free, non-sublicensable (except as necessary to use the Work Product), non-transferable (except to a successor in interest), worldwide, perpetual license to use such Consultant Tools solely as part of the Work Product.
|
||||
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.
|
||||
Limitation of Liability
|
||||
HansonXyz’s liability for any claim arising out of this agreement shall not exceed the total compensation paid under this agreement. In no event shall HansonXyz be liable for any consequential, incidental, special, or punitive damages, including lost profits or business interruption.
|
||||
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.
|
||||
Prior Agreement Supremacy
|
||||
In the event of any ambiguity, conflict, or omission in this agreement, the terms of the previously executed ongoing hosting and maintenance agreement between HansonXyz and Landproz shall govern and prevail.
|
||||
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.
|
||||
Severability
|
||||
If any provision of this agreement is found to be invalid or unenforceable, the remaining provisions shall continue in full force and effect.
|
||||
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.
|
||||
|
||||
|
||||
|
||||
IN WITNESS WHEREOF, the parties have executed this Agreement:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user