A first version already exists. This phase makes it ready for real clients.
This phase
£3,500
2–3 week completion sprint
Daryl has already made significant progress building Elite Private Services, a private concierge marketplace designed to connect ultra-high-net-worth individuals, family offices and their representatives with vetted specialist service providers.
The business model combines paid membership with a managed marketplace. Clients submit confidential service briefs, approved specialists propose against them, and EPS remains in the middle to review the options, broker the final match and control the commercial relationship. Revenue comes from recurring subscriptions alongside a commission on completed engagements.
A strong first version of the platform has already been created. The next stage is therefore not to rebuild everything from scratch, but to close the gaps between what exists today and the core experience defined across the PRD, TRD, User Stories and User Journey Flows.
Unlike an open marketplace, the intention is deliberately to keep EPS involved throughout the relationship. Clients and specialists should not be able to bypass EPS or establish an unmanaged relationship directly through the platform. This was one of the main challenges identified during our initial conversation.
The EPS model
- Paid membership across Silver, Gold and Black tiers
- Confidential service briefs submitted by approved principals
- Vetted specialists proposing against suitable briefs
- EPS brokering the match and setting the engagement value
- Commission on completed engagements alongside subscription revenue
- A deliberately closed marketplace, not an open directory
The journey that has to hold together
- Application
- Approval
- Membership
- Brief
- Proposal
- EPS-approved engagement
- Payment
- Completion
- Review
Completion, not rebuild
“Preserve as much of Daryl's existing work as possible, while making sure the underlying foundations are appropriate for real customers, sensitive information and live payments.”
Work from what exists
Keza Studio will work from the existing EPS application rather than unnecessarily rebuilding completed work. Everything already built is assessed for what can be retained, improved or completed.
Build against the documentation
The PRD, TRD, User Stories and User Journey Flows already produced for EPS become the reference point. Existing functionality is mapped against them so the gaps are explicit rather than assumed.
Production, not prototype
Real client information, real specialists and real payments demand a stronger standard than a first version needs. Security, permissions and payment handling are treated as core scope, not polish.
EPS keeps control
The platform is left with a clear technical foundation and appropriate ownership of code and infrastructure, rather than becoming unnecessarily dependent on a single development platform.
EPS provides
EPS provides- Provide access to the existing application, database and documentation
- Confirm commercial rules: tiers, commission and deposit expectations
- Review completed journeys and give consolidated feedback
- Supply real content, categories and any brand assets required
- Hold the accounts for payment processing, email and hosting
Keza Studio handles
Included- Technical review and consolidation of the existing build
- Completion of the principal, specialist and admin experiences
- Payments, deposits, balances and commission handling
- Notifications, security, permissions and data protection
- Mobile optimisation and Progressive Web App setup
- Structured QA, deployment support and the documentation handover pack
Existing platform review and technical consolidation
What the review covers
- Review of the existing project and codebase
- Review of the existing database structure and integrations
- Review of the PRD, TRD, User Stories and User Journey Flows
- Mapping existing functionality against the agreed product requirements
- Identifying incomplete, disconnected or insecure functionality
- Removing or refactoring unnecessary technical debt where required
- Establishing a clear technical foundation for future development
- Ensuring EPS retains appropriate ownership and control of its code and infrastructure
The output is a clear picture of what is genuinely finished, what needs completing and what needs correcting before real users are let in.
Principal and member experience
Access & membership
- Account registration and secure sign-in
- Membership application
- Admin approval before membership activation
- Silver, Gold and Black membership tiers
- Membership checkout and subscription management
- Member dashboard
Briefs & proposals
- Creation of confidential service briefs
- Service category, budget, location, timeframe and urgency capture
- Viewing active and historic briefs
- Receiving and reviewing specialist proposals
- Accepting or declining proposals
- Cancelling or closing a brief
- NDA protection for appropriate sensitive briefs
Engagement & payment
- Booking confirmation
- Deposit payment
- Engagement status visibility
- Final payment flow where required
- Specialist review and rating after completion
- Billing history and payment management
- Mobile-responsive member experience
A principal can move from application through to review without ever falling outside the platform.
Specialist and provider experience
Completed on the supplier side
- Specialist registration and application
- Company and provider information capture
- Admin vetting and approval
- Partner subscription activation
- Specialist dashboard
- Access to suitable open briefs
- NDA acceptance before viewing protected briefs
- Proposal submission
- Proposal status tracking
- Visibility of relevant engagement information
- Notifications when proposal or engagement status changes
- Public provider profile information where appropriate
- Protection of client personal information and EPS commercial information
The specialist journey remains controlled by EPS rather than operating as an unrestricted public marketplace.
EPS admin and matching portal
People
- Secure admin access
- Membership application management
- Approve, reject or waitlist prospective members
- Specialist application and vetting management
- Provider approval, activation and disabling
Matching
- View submitted service briefs
- View proposals associated with each brief
- Select and confirm the appropriate specialist
- Set the final engagement value
- Create and manage bookings
- Move engagements through their lifecycle
Commercial control
- View deposits and payment status
- Manage relevant marketplace statuses
- Visibility over users, providers and marketplace activity
- Commission visibility for EPS administrators only
- Commission configuration and control where required
- Operational controls that keep EPS between client and specialist
EPS is designed as a human-brokered marketplace. The admin does not merely moderate the platform: EPS controls the match and sets the engagement value before the booking is created.
Payments and marketplace commercial flow
Deposit
25%
on confirmed engagement
Deposit
The principal pays the 25% deposit once EPS confirms the match and sets the engagement value.
Delivery
The engagement runs through its lifecycle with status visible to the principal, the specialist and EPS.
Balance
The remaining balance is settled where required, with billing records and receipts on both sides.
Commission
EPS retains its agreed commission, calculated and reported only to EPS administrators.
Payment functionality completed
- Membership subscription payments
- Partner subscription payments
- Monthly and annual plan handling where applicable
- Secure checkout
- Deposit collection
- Final balance collection where required
- Payment status tracking
- Billing records and payment receipts
- Commission calculation
- EPS commission protected from client and provider visibility
- Specialist net-payment calculation
- Payment webhook handling and reconciliation
- Protection against duplicate or incorrect transactions
Notifications and platform communication
Events covered
- Application received
- Application approved, rejected or waitlisted
- Specialist approved
- New brief available where appropriate
- New proposal received
- Proposal accepted
- Proposal declined
- Match confirmed by EPS
- Deposit required
- Deposit received
- Engagement started
- Engagement status changed
- Engagement completed
- Final payment required
- Review requested
- Payment failure or other important billing event
Email acts as the primary communication channel, with in-platform notification behaviour added where appropriate, so relevant parties are kept informed as the marketplace changes state.
Security, permissions and data protection
Reviewed and strengthened
- Server-side user role assignment
- Principal, specialist and administrator permissions
- Row-level database security
- Prevention of unauthorised cross-user data access
- Protection of commission and commercially sensitive information
- Admin-only operations
- Secure payment operations
- Authentication and session handling
- Sensitive service brief access
- NDA-based access controls
- Input validation
- Protected API and server operations
- Appropriate handling of personally identifiable information
- Error handling around sensitive actions
Roles in particular will be controlled server-side rather than allowing a user to grant themselves provider or administrative-style access through client-controlled actions.
Mobile optimisation and Progressive Web App
- Improved mobile responsiveness
- App-style mobile layout
- Add-to-home-screen capability
- PWA configuration
- Appropriate mobile navigation
- Mobile-friendly dashboards and forms
- Push-notification readiness where supported
- Performance optimisation across phone, tablet and desktop
This gives EPS an app-like experience without immediately introducing the cost and complexity of maintaining separate iOS and Android applications.
AI concierge and personalisation
Reviewed and completed for production
- AI concierge experience
- Persistent concierge conversations
- Interest-based personalisation
- AI-assisted recommendations
- Appropriate error and rate-limit handling
- Review of the existing AI integration for production use
Where practical within this phase, the concierge experience will be better connected to the wider product journey so it supports rather than sits separately from the core marketplace.
QA, testing and production readiness
Testing covers
- Registration and authentication
- Permissions and role access
- Membership application
- Membership subscriptions
- Specialist onboarding
- Brief creation
- NDA flows
- Proposal submission and acceptance
- Admin matching
- Booking creation
- Payments
- Notifications
- Reviews
- Mobile responsiveness
- Error and empty states
- Basic security scenarios
The objective is to deliberately use the platform in unexpected ways and surface bugs before EPS customers do.
Project documentation and handover pack
The handover pack
- Product Requirements Document
- Technical Requirements Document
- MVP Scope
- User Journey Flows
- User Stories
- Design System
- Development Roadmap
- Monetisation Plan
- Launch Plan
- User Acquisition Plan
- Growth Plan
Several of these documents have already been produced during discovery and platform review. They will be updated to reflect the final product delivered, with the remaining documents completed as part of handover.
These documents are strategic handover deliverables. Ongoing marketing execution, paid media management, content production, sales outreach or ongoing growth-team delivery are not included unless separately agreed.
Timeline
- W1
Foundation & core journeys
Keza StudioTechnical review, architecture and security corrections, authentication and permissions, principal and specialist onboarding, admin controls and the core marketplace workflow.
- W2
Transactions & operations
Keza StudioProposal and matching lifecycle, payments, deposits and balance handling, notifications, admin operations, mobile and PWA improvements.
- W3
Final review, if required
BothEnd-to-end QA, security and edge-case testing, bug fixing, deployment preparation, documentation finalisation and final handover.
The objective is to get EPS to the point where real users can begin testing the platform and exchanging money through it as quickly as possible, without compromising the foundations required for the platform to grow.
Investment
Total for this phase
£3,500
split across two stages
On acceptance
£1,750
Secures the project and begins work, starting with the technical review and core journeys.
On completion
£1,750
Payable once the agreed platform is ready for launch and handover.
What the fee covers
- Review and consolidation of the existing EPS build
- Implementation against the agreed PRD, TRD, User Stories and User Journeys
- Completed principal/member experience
- Completed specialist/provider experience
- EPS admin and matching experience
- Membership and provider vetting workflows
- Service brief and proposal lifecycle
- NDA-gated confidential briefs
- Booking and engagement workflow
- Subscription and payment integration
- Deposit and balance payment journey
- Commission handling
- Lifecycle email notifications
- Improved security and role permissions
- Mobile optimisation and Progressive Web App setup
- Review and refinement of existing AI functionality
- Structured QA and bug fixing
- Deployment and production-readiness support
- Complete product, technical, launch and growth documentation pack
Terms
- Payment can be split into two stages: £1,750 upfront and £1,750 on completion.
- Any third-party running costs such as payment processing fees, hosting, email delivery, identity verification or external API usage remain payable directly by EPS to the relevant providers.
- The fee covers the completion sprint described in this proposal, including QA and the documentation handover pack.
Scope management
The PRD and supporting documentation describe both the core launch product and a number of wider product capabilities.
This proposal is intended to complete and productionise the current EPS platform around the core marketplace journey and the functionality already substantially represented within the existing application.
Where a feature in the documentation represents a materially new system rather than completion or refinement of the existing platform, Keza Studio will discuss it with Daryl before undertaking significant additional work.
Materially new systems
Discussed case by caseCapabilities described in the documentation that go beyond completing the existing platform are discussed and agreed before work begins.
Native iOS and Android apps
Future phaseThis phase delivers a mobile-first Progressive Web App rather than separate native applications.
Marketing and growth execution
Separately agreedThe Launch, User Acquisition and Growth Plans provide strategic direction. They are not an ongoing marketing, sales or growth delivery service.
Third-party running costs
Payable by EPSPayment processing fees, hosting, email delivery, identity verification and external API usage are paid directly by EPS to those providers.
This approach is intended to prevent unnecessary feature creep and keep both parties clear on exactly what needs to be completed for the first launch-ready version of EPS.
Outcome
At the end of this phase, EPS has a platform where
- Principals can apply, subscribe and submit confidential briefs
- Specialists can be vetted, subscribe and respond to suitable opportunities
- EPS remains in control of the relationship and matching process
- Engagements can be converted into bookings
- Money can move through the platform securely
- Relevant users are notified as the engagement progresses
- EPS can manage the marketplace through its own administrative controls
- The application works properly across desktop and mobile
- The underlying foundations are better suited to real customers and future growth
The goal is not simply for the screens to look finished. The goal is for EPS to be ready to begin onboarding real users, facilitating real engagements and generating revenue with significantly more confidence in what is happening behind the scenes.
Next steps
- 01Confirm acceptance of this proposal and the intended start date.
- 02Keza Studio sends the project agreement and the invoice for the initial £1,750 payment.
- 03Access is shared to the existing application, database, documentation and any third-party accounts.
- 04The completion sprint begins with the technical review against the agreed documentation.
- 05Core journeys, payments and admin controls are completed and reviewed with Daryl.
- 06Final QA, deployment preparation and the documentation handover pack complete the phase.
EPS will finish this engagement with both a working platform and the documentation required to operate, develop, launch and grow it with clarity: a clear blueprint for running the launch version, prioritising future development, acquiring the first users and growing beyond launch.