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).


