Make participation explicit
Course search, round creation, invitations, and RSVP decisions form a connected member journey. Figure 1 shows the sequence and the product scope.
Explore the application ↗Professional portfolio / Application development
Guild of Golf
Guild of Golf is an application developed by Steven Stanek under INOV8 LLC to help golfers organize rounds and coordinate participation.
Open the Guild of Golf application
From operational workflows to useful software.
I bring a background in enterprise technology, systems integration, and technical leadership to application development. My work centers on turning loosely defined needs into practical workflows, with attention to usability, validation, and operational reliability.
Guild of Golf applies that approach to a familiar coordination problem. My role spans product direction, workflow design, and iterative development with AI-assisted coding tools. I define the user experience, review behavior, and guide improvements as the product evolves.
Project context: An INOV8 venture also being developed as an individual course project. I am working independently, using the project plan and design to guide development. Course search, round creation, and invitations are the course priorities.
User accountsCourse searchRound managementInvitations + RSVP
Organize the round. Coordinate the group.
Golf rounds often begin across separate messages, course searches, and availability checks. Guild of Golf brings those steps into one application so a host can define a round and golfers can coordinate who is participating.
Implemented functionality: Members can create accounts, search for courses, create and manage rounds, invite other members, request a place, and accept or decline RSVP activity. Server-side checks prevent duplicate participation and conflicting rounds for golfers already hosting, confirmed, or awaiting a decision at the same time.
Technology: The application uses Python and FastAPI for the API and web service, SQLAlchemy for data access, Pydantic for request validation, SQLite for application data, and a responsive HTML, CSS, and JavaScript frontend.
Scope: Complete and check the core golfer workflows before taking on broader feature ideas. The caddie assistant, transactional email delivery, and expanded account recovery are separate from the current course priorities.
Development underway. Validation next.
Development follows the project plan and design, with remaining changes focused on course search, creating rounds, and invitations. Testing and portfolio documentation are still on the work list. The capabilities described here do not represent a completed acceptance-test cycle.
October 26–November 1 plan: Work through the remaining task list, update the schedule, and test course search, round creation, invitations, and account permissions. Record issues and recheck duplicate-round prevention.
Duplicate-round prevention: The Week 5 risk register marks this risk as mitigated. Keep the existing changes in place and recheck them as round creation evolves.
Portfolio evidence: The overview, individual role, diagrams, and application link are available here. Application screenshots and recorded test results are outstanding and will be added as they become available.
Risks being tracked: Available project time, application and external-link availability, tester participation, protection of saved data, account and invitation permissions, and scope growth. Planned controls include backups before changes, checks with separate accounts and while signed out, and prioritizing required features.
Skills & project artifacts
Connect each skill to the work.
The application is the primary project artifact. The workflow and architecture diagrams below explain how its features support the coordination problem.
Connect interface and data
A responsive web interface uses a Python API and a relational data model. Figure 2 identifies the responsibilities of each layer.
View the architecture ↓Protect the shared schedule
Duplicate participation and schedule-conflict checks keep round coordination consistent. These rules are part of the implemented functionality described above.
Review the implementation ↑Finish the agreed features first
The Week 5 plan keeps broader ideas separate from the course requirements. The caddie assistant is an extension prototype outside that scope; core workflows, validation, and portfolio evidence take priority.
Review the development plan ↑- Member interfaceHTML · CSS · JavaScript
Search, forms, round details, and participation controls.
- Application servicePython · FastAPI · Pydantic
Authenticated requests, validation, and round coordination rules.
- Application dataSQLAlchemy · SQLite
Persistent records for members, courses, rounds, and participation.
Assistance should preserve user choice.
Round planning involves more than extracting a course and a date. A golfer needs to know what is proposed, what is confirmed, and what still needs a decision. The caddie concept makes that distinction visible through a draft, a review step, and explicit confirmation.
The same principle applies to the broader product: invitations and RSVP decisions should represent a member’s intent. A useful assistant can reduce effort while keeping those choices clear.
Next evaluation: Observe first-time users completing course search and round coordination, identify where they hesitate, and use those findings to improve guidance.
Experience behind the project.
My broader experience includes enterprise collaboration platforms, systems integration, workflow standardization, and technical team leadership. Guild of Golf demonstrates how I apply that operational perspective to a user-facing application.
View Steven Stanek’s LinkedIn profile ↗
For project questions or a discussion of relevant experience, contact INOV8.
Application capabilities · validation in progress
01User accounts and member profiles
02Golf course search
03Round creation and management
04Duplicate-round prevention
05Schedule-conflict checks
06Member invitations
07RSVP requests and decisions
08Responsive web interface
Have a problem worth solving?