Prepared for: Tabitha Thompson VP Operations Las Vegas Lighting

Prepared for: Juan Carlos Torres URLOOH LLC

Smart Contract ID: 0.12-27 BTC

Date: August 27, 2025

Hi Tabitha,

Thank you again for the opportunity to work with you on this important next step for Las Vegas Lighting. After careful research and planning, I’ve prepared a full proposal outlining the design and development of a custom ecommerce website, CMS, and secure customer portals, all hosted on AWS for maximum performance and cybersecurity.

The proposal also includes in-person support for inventory analysis and product placement (covering your 15,000+ products), weekly training sessions, and long-term optimization. Most importantly, my commitment doesn’t end after launch — I will serve as your lifetime administrator to ensure continued growth, updates, and reliable system management. I believe this solution will not only strengthen your online presence but also streamline operations, improve customer engagement, and deliver a lasting foundation for growth.

I’d love to schedule a time to review the proposal with you in detail and answer any questions you may have. Please let me know what day and time works best for you.

With appreciation,
Juan Carlos Torres

PROJECT OVERVIEW: Custom Website CMS using AWS Hosting
Introduction Las Vegas Lighting is ready to take the next step in its digital growth. Customers today expect not only quality products but also a smooth, secure, and reliable way to shop and manage their accounts online. This proposal is designed to provide exactly that: a custom ecommerce website combined with secure customer portals to improve both sales and customer experience. I’m also pleased to share that I was able to locate what appears to be the original domain name, www.lasvegaslighting.net. Securing this domain will allow the business to strengthen its brand identity and give customers the confidence of shopping through a trusted, recognizable address. The new platform will be hosted on Amazon Web Services (AWS) for speed, reliability, and security. It will allow Las Vegas Lighting to manage products, process orders, and support customers without interrupting current operations. I, Juan Carlos Torres, will personally build and manage the project from start to finish, including six months of ongoing support and in-person training for your staff. This ensures that once the system is launched, your team will have the confidence and knowledge to use it effectively. This project is not just about building a website—it’s about creating a foundation for growth, stronger customer relationships, and a more powerful online presence for Las Vegas Lighting.
PROPOSAL OBJECTIVE: A Proposal for Custom Website Build, CMS, and Seamless AWS Hosting Integration
The primary objective of this proposal is to outline a comprehensive plan for the design and development of a custom ecommerce website and content management system (CMS) for www.lasvegaslighting.net, together with secure customer portals to improve account management and customer service. With a large inventory of over 15,000 products, Las Vegas Lighting requires a robust, scalable, and highly secure platform. By hosting the solution on Amazon Web Services (AWS), the project ensures enterprise-level performance, industry-leading cybersecurity, and compliance with best practices for protecting sensitive ecommerce data such as payments, customer accounts, and return processing. This approach will allow Las Vegas Lighting to confidently scale its online presence while safeguarding both business and customer information. Objective List: ✔ Website Design and Development ✔ Design a modern, user-friendly interface that reflects the Las Vegas Lighting brand identity ✔ Develop a responsive design optimized for desktop, tablet, and mobile ✔ Implement SEO best practices to improve visibility across search engines ✔ Integrate social media channels for extended engagement and marketing ✔ Ensure architecture is designed for efficient browsing of 15,000+ products ✔ Custom Content Management System (CMS) ✔ Develop a custom CMS hosted on AWS, benefiting from its multi-layered security infrastructure including firewalls, DDoS protection, and automated monitoring ✔ Provide intuitive tools for non-technical staff to manage inventory, pricing, and content at scale ✔ Enforce encryption of data at rest and in transit to secure sensitive customer and product information ✔ Customer Portals ✔ Implement secure, role-based access portals for contractors, business accounts, and retail customers ✔ Provide features including order history, invoices, and returns management ✔ Incorporate AWS Identity & Access Management (IAM) controls to prevent unauthorized access ✔ Encrypt authentication and payment workflows to safeguard customer financial data ✔ Cybersecurity for Ecommerce & Returns ✔ Protect all transactions and return requests using AWS’s compliance-ready infrastructure (PCI DSS, ISO 27001, GDPR standards) ✔ Ensure return requests are logged and tracked with audit trails, minimizing fraud ✔ Integrate SSL/TLS certificates to provide customers with secure checkout and portal login experiences ✔ Deploy AWS Shield and WAF (Web Application Firewall) to prevent data breaches, unauthorized access, and denial-of-service attacks ✔ Testing and Deployment ✔ Conduct thorough cross-device and browser testing ✔ Perform penetration and load testing to validate security and stability under heavy traffic ✔ Apply vulnerability scanning to detect and patch risks before launch ✔ Deploy live with monitoring tools that continuously track uptime, performance, and security threats ✔ Project Management ✔ Establish a phased timeline with milestones and deliverables ✔ Provide regular project updates to Las Vegas Lighting management ✔ Use project management tools to monitor workflows and deadlines ✔ On-Site Training and Support ✔ Onboarding: Walkthrough of the website, CMS, and customer portals with emphasis on cybersecurity practices ✔ Weekly In-Person Support Visits: Ongoing technical training and security guidance ✔ Performance & Security Reviews: Routine checks to ensure the system meets operational and compliance requirements ✔ Feedback & Continuous Improvement: Collect input from staff, refine workflows, and strengthen data protection Strategic Impact By leveraging AWS cloud hosting and cybersecurity infrastructure, Las Vegas Lighting gains not only a modern ecommerce presence but also the trust and reliability that today’s customers demand. This solution ensures safe online shopping, protected customer accounts, and a transparent returns process that minimizes risk. The result is a secure, scalable, and future-ready platform that improves operations, builds stronger customer relationships, and supports long-term growth.
PROJECT ONE: Custom e-Commerce Website CMS using AWS Hosting
Project One The Las Vegas Lighting ecommerce and customer portal project will deliver a secure, scalable, and customer-focused digital platform hosted on AWS. With a large inventory of 15,000+ products, the solution will include a custom website, CMS, and customer portals designed for both retail and business clients. Emphasis will be placed on cybersecurity, inventory accuracy, and staff empowerment through in-person training. The project begins September 1, 2025, and will run for 6 months with phased milestones.
Project One Overview: Month 1 (Sept 2025): Planning & Infrastructure Setup ✔ Secure www.lasvegaslighting.com domain and configure AWS hosting environment ✔ Define system architecture for ecommerce, CMS, and customer portals ✔ Create sitemaps, user flows, and detailed wireframes for customer journeys ✔ In-person kickoff meeting with leadership team to confirm business goals and workflows Month 2 (Oct 2025): Website Framework & Initial CMS Build ✔ Develop homepage, category pages, and product catalog framework ✔ Build responsive layouts optimized for desktop, tablet, and mobile ✔ Implement CMS structure for product entry and management ✔ Begin inventory analysis on-site (review product categories, SKUs, and specifications) ✔ Initial staff orientation session to introduce CMS basics Month 3 (Nov 2025): Product Integration & Ecommerce Core ✔ Conduct in-person product placement into CMS (uploading descriptions, images, pricing for thousands of SKUs) ✔ Complete ecommerce functionality (shopping cart, checkout, secure payment gateway) ✔ Implement SEO optimization across key product pages ✔ Develop role-based portal framework for business accounts and contractors ✔ On-site staff training: product uploads, image formatting, and CMS updates Month 4 (Dec 2025): Customer Portals & Return Workflow ✔ Launch secure portals with account creation, order history, invoices, and returns tracking ✔ Configure AWS security (IAM, encryption, SSL/TLS) for portals and payments ✔ Enable automated notifications (order confirmations, returns approval, shipment updates) ✔ Perform second round of inventory validation and product data quality checks in person ✔ Advanced staff training: order processing, customer service workflows, and returns handling Month 5 (Jan 2026): Testing, Security, & Optimization ✔ Conduct cross-browser/device testing for all ecommerce and portal features ✔ Perform load testing for 5,000+ product catalog and high-volume cart transactions ✔ Carry out penetration testing, vulnerability scans, and patch management ✔ On-site review of staff workflow performance and system adoption ✔ Train staff on cybersecurity best practices (password policies, phishing awareness, handling sensitive data) Month 6 (Feb 2026): Deployment, Training, & Post-Launch Support ✔ Deploy live website, CMS, and portals with AWS Shield and WAF protection ✔ Conduct final inventory reconciliation to confirm accuracy of listings, pricing, and availability ✔ Weekly in-person support sessions for troubleshooting and advanced training ✔ Train staff on analytics dashboards (sales tracking, customer insights, product performance) ✔ Collect post-launch feedback and implement refinements ✔ Final project review: confirm system stability, customer satisfaction, and handover documentation Strategic Outcome By the end of this 6-month project, Las Vegas Lighting will have a fully secure, enterprise-grade ecommerce platform capable of managing its 15,000+ product inventory and delivering seamless customer experiences through secure portals. The system will be built on AWS infrastructure, ensuring that all transactions, customer accounts, and returns are protected by industry-leading cybersecurity. The in-person inventory onboarding and product placement will guarantee accuracy across the catalog, while hands-on staff training will empower your team to manage daily operations confidently. In addition, ongoing support will provide continuous refinements to improve usability, security, and performance. Most importantly, this project establishes not just a platform but a long-term partnership: Las Vegas Lighting will benefit from a dedicated lifetime administrator (Juan Carlos Torres) committed to continued development, system optimizations, and ensuring the platform adapts to future business needs. This guarantees that the solution remains sustainable, scalable, and aligned with the company’s growth for years to come.
INVESTMENT: Project One Cost: $13,500.00 USD
TOTAL INVESTMENT: Total Proposal Cost: $13,500.00 USD Payment Structure To make this investment accessible and manageable, the following payment schedule is proposed: ✔ Down Payment: $3,500.00 USD due upon acceptance of proposal ✔ Remaining Balance: $10,000.00 USD, payable in 12 monthly installments of $833.33 USD This structure ensures that Las Vegas Lighting can move forward with a secure ecommerce system while keeping payments spread out in a predictable and sustainable schedule.

I’d like to make sure it’s clear that the document I’ve shared is only a proposal for your review and consideration. It has been priced at a very modest rate — calculated at the equivalent of a part-time employee in Nevada earning minimum wage — in order to make this project as accessible as possible while still covering the scope of work.

By confirming that you’ve read the proposal, it should not be interpreted as a binding contract. No work will begin until terms are formally agreed upon in writing and both parties approve a final contract.

This proposal is simply a detailed outline of the project vision, scope, and investment structure to help guide decision-making.

← Back

Thank you for your response. ✨

Thank you for reviewing, and I look forward to hearing your feedback.

MGM Resorts Coupa Supplier Onboarding

Responsibility Matrix & 6-Week Execution Plan – Las Vegas Lighting

MGM Resorts Coupa Supplier Form

Exact Task Ownership & Responsibilities

1. Supplier Profile & Company Information

Owned by: Grace / Internal Business Team

1.1 Supplier legal name, physical address, city, state, zip
1.2 Business contact name, title, phone, and email
1.3 Technical contact designation (name/title only; JT handles technical details)
1.4 Support contact name, title, phone, and email
1.5 General company information and internal company contacts

Reason: These are legal, administrative, and operational facts MGM requires from the supplier record itself, not from the web platform.

2. Punchout Configuration (Questionnaire – cXML Section 2)

Split Ownership

2A. Business Decisions — Grace / Team

2.1 Approval to participate in Coupa Punchout
2.2 Confirmation of supplier identity type (DUNS vs alternate)
2.3 Confirmation that MGM may access a hosted catalog
2.4 Business approval of production vs test readiness

2B. Technical Execution — JT

2.5 Supplier Punchout URL (test & production)
2.6 Secure order posting URL
2.7 Shared secret creation and management
2.8 Supplier domain and identity configuration
2.9 Buyer identity mapping (MGM-T / MGM-P)
2.10 Session handling and cart-return logic

Reason: Punchout URLs, secrets, and session logic are web and system-level integrations governed by cXML standards.

3. Invoice Method Selection (Questionnaire – cXML Section 3)

Owned by: Grace / Business Team

3.1 Selection of ONE option:
• Coupa Supplier Network
• cXML Invoice Integration
3.2 Business approval of invoicing workflow
3.3 Confirmation of payment terms policy

Owned by: JT

3.4 Invoice endpoint configuration (test & production)
3.5 Supplier identity and domain for invoice cXML
3.6 Buyer (MGM) identity mapping
3.7 Shared secret implementation
3.8 Validation of invoice submission and response handling

4. Timeline & Process Questions (Questionnaire – cXML Section 4)

Joint Ownership, with Clear Roles

4A. Business Inputs — Grace / Team

4.1 Business readiness date for production orders
4.2 Internal approval requirements before production
4.3 Confirmation of when MGM may place live orders
4.4 Confirmation of when MGM may receive invoices

4B. Technical Inputs — JT

4.5 Timeline to configure test PO and invoice
4.6 Timeline to receive and process test POs
4.7 Requirements for promoting to production
4.8 System fallback procedures during outages

5. Punchout-Specific Questions (Questionnaire – cXML Section 4)

Split Ownership

5A. Product & Brand Decisions — Grace / Team

5.1 Which products are approved for MGM catalog
5.2 Which items are excluded from punchout
5.3 Logo approval and brand asset delivery
5.4 Units of measure policy (EA, BOX, etc.)

5B. Technical Enforcement — JT

5.5 Catalog filtering logic
5.6 SKU visibility rules
5.7 Enforcement of units of measure in catalog
5.8 Mapping of items to Coupa structure

6. Purchase Order (PO) Handling (Questionnaire – cXML Section 4)

Split Ownership

6A. Business Policy — Grace / Team

6.1 Requirement for location/address IDs
6.2 Shipping term acceptance policy
6.3 Payment term handling policy
6.4 Whether PO acknowledgements are required
6.5 Policy for non-cXML (manual) POs

6B. Technical Handling — JT

6.6 PO parsing and validation
6.7 Address ID mapping
6.8 Payment term ingestion (even if informational)
6.9 Error handling and retries
6.10 Designated technical escalation contact

7. cXML Purchase Order, Response & Invoice Samples

(Questionnaires Sections 5–14)

Owned by: JT (Technical Authority)

7.1 Implementation of required cXML fields
7.2 Validation of required attributes (orderID, quantity, currency, ItemID, SupplierPartID)
7.3 UNSPSC / classification mapping support
7.4 Accounting segment handling (pass-through or storage)
7.5 Invoice detail request construction
7.6 Tax, shipping, discount, and net amount logic
7.7 OrderResponse handling (status 200 OK)
7.8 Logging, monitoring, and audit trail creation

Reason: These sections are technical reference models that must be implemented in code, not filled out manually.

8. Final Submission & MGM Coordination

Joint Responsibility

8.1 Grace / Team approves final business data
8.2 JT confirms technical readiness and testing
8.3 JT submits technical confirmations as needed
8.4 Grace submits completed form to MGM contact

9. Overall Delivery Timeline

9.1 Total expected delivery timeline: six (6) working weeks
9.2 Weeks 1–2: Business data completion + technical setup
9.3 Weeks 3–4: Test environment validation
9.4 Weeks 5–6: Production readiness and MGM sign-off

Table 1 — Responsibility Matrix

MGM Form Section	Responsibilities & Owner
Supplier Profile & Company Information	Grace and the Las Vegas Lighting internal team are responsible for providing the legal business name, address, business contact, support contact, technical contact designation, and general company information.
Punchout Configuration (cXML Section 2)	Grace and the internal team approve punchout participation, supplier identifiers, and catalog eligibility. JT (Juan Carlos Torres) configures punchout URLs, secure order posting URLs, shared secrets, buyer/supplier identities, and punchout session handling.
Invoice Integration (cXML Section 3)	Grace and the internal team select the invoicing method and approve payment terms. JT (Juan Carlos Torres) configures invoice endpoints, domains, identities, secrets, and validates cXML invoice transmission.
Timeline, Process, and Support (cXML Section 4)	Grace and the internal team define business readiness dates, approvals, and downtime procedures. JT (Juan Carlos Torres) defines technical timelines, production prerequisites, monitoring, and escalation paths. Final dates are jointly approved.
PO Rules, Punchout Rules, and cXML Samples (Sections 5–14)	Grace and the internal team define product inclusion, exclusions, logo assets, units of measure, and PO business policies. JT (Juan Carlos Torres) implements cXML PO, OrderResponse, and Invoice schemas, required fields, accounting segments, and validation logic.
Final Submission to MGM	Grace and the internal team submit the completed form to MGM. JT (Juan Carlos Torres) confirms technical readiness and supports MGM validation. Final approval is a joint responsibility.

Table 2 — Week 1–6 Execution Checklist

Week	Key Deliverables & Owner
Week 1	Business profile, contacts, supplier identifiers, invoicing option selection, and punchout approval completed. Owner: Grace and Las Vegas Lighting internal business team.
Week 2	Test environment prepared, punchout URLs defined, shared secrets created, buyer and supplier identities configured. Owner: JT (Juan Carlos Torres).
Week 3	Punchout flow operational, cart return validated, SKUs, pricing, inventory, and units of measure mapped and enforced. Owner: JT (Juan Carlos Torres) with product approvals from Grace.
Week 4	Test purchase orders received and parsed, OrderResponse acknowledgements validated, manual PO handling policy confirmed. Owner: JT (technical) and Grace (business policy).
Week 5	Test invoices submitted via cXML, PO-to-invoice matching validated, monitoring and production plan completed. Owner: JT (Juan Carlos Torres).
Week 6	Production configuration completed, final review performed, MGM submission completed, and readiness for live orders confirmed. Owner: Grace and internal team (submission), JT (technical readiness), joint sign-off.