ConnectX and ArtWorksIT
Hold tightHi there!

Proposal

30 August 2026

Proposed

Wedding & Corporate
Event Planning Platform

Prepared byArtWorksIT
Project start31st August 2026
Project completionMid-November 2026
Project timeline10 to 11 weeks
01 / Project Objective

Project Objective

ArtWorksIT proposes to design and develop Phase One of a web-based event planning and vendor management platform for ConnectX.

The proposed platform will allow users to create and plan events, define individual sub-events, discover and select vendors, facilitate enquiries and negotiations, and track the progress of their event through a centralised interface.

The initial phase is intended to establish the core planning and marketplace infrastructure while keeping the system flexible enough to support future enhancements, including deeper operational workflows, hybrid or offline service models, and AI-assisted functionality.

The platform is proposed to support both wedding and corporate events. While the underlying planning flow will remain similar, the experience can accommodate the different requirements and contexts of each event type.

Co-Founders

Prranit Bhanne and Mukesh Tekchandani

02 / Project Scope & Timelines

Project Scope & Timelines

A key objective will be to ensure that the platform is not approached simply as a marketplace for venues or individual vendors. The proposed experience will instead begin functioning as an event planning platform from Phase One.

Proposed project start31st August 2026
Proposed project completionMid-November 2026
Project timelineApproximately 10 to 11 weeks
Phase
31 Aug7 Sep14 Sep21 Sep28 Sep5 Oct12 Oct19 Oct26 Oct2 Nov9 Nov
01Research & Product Definition
02Wireframing & User Experience
03Design & Prototyping
04Development
05Testing & Launch

The parallel tracks indicate where project stages overlap.

31 Aug – 13 Sep 2026

Research & Product Definition

2 weeks

We will begin by understanding the complete system, its users, dependencies and the actions that may need to take place across the platform, both within Phase One and in future iterations.

The research phase will establish the core product structure and identify the information, fields, workflows and dependencies required across customers, vendors and the ConnectX administration team.

A key objective will be to ensure that the platform is not approached simply as a marketplace for venues or individual vendors. The proposed experience will instead begin functioning as an event planning platform from Phase One, helping users understand what needs to happen, what has been planned, what has been booked and what remains to be completed.

Deliverables

Product structure, functional mapping and low-fidelity product direction.

31 Aug – 13 Sep 2026

Wireframing & User Experience

Included within the initial product definition and wireframing phase

Based on the research, we will map the primary user journeys and translate the proposed product structure into low-fidelity wireframes.

This stage will define the key screens, data points, fields, navigation and control flows across the customer, vendor and administrative interfaces.

The experience will account for event creation, sub-events, vendor discovery, vendor selection, proposals, negotiations, notifications and event progress. We will also define how users can visualise the overall state of their event and understand the completion of key planning activities.

The wireframes will also help establish how the platform can evolve beyond the initial implementation without requiring the underlying product structure to be rebuilt.

Deliverables

Wireframes and user-flow definitions.

4 Sep – Mid-Oct 2026

Design & Prototyping

A little over one month

Once the product structure and wireframes have been established, we will develop the visual language and interface design for the platform.

This will include typography, layout, interface components, graphics, visual hierarchy and interaction patterns. Particular attention will be given to making a data-heavy application understandable and accessible, with information presented in a way that allows users to quickly understand what is happening within their event.

The primary usage environment is expected to be desktop, while the interface will also be designed responsively for mobile devices. Mobile layouts will focus on condensing event information and navigation without compromising usability.

The designs will be presented to the Client for review and feedback. Once the design direction is sufficiently defined, the relevant screens will be frozen for development.

Deliverables

High-fidelity interface designs and interactive prototypes.

21 Sep – Mid-Nov 2026

Development

Runs progressively through the development period

Development will begin progressively alongside the product definition and design process rather than only after the visual design stage is complete.

Because the proposed platform is backend and workflow heavy, the underlying systems, dashboards, vendor structures, proposal mechanisms, communications and supporting workflows will begin taking shape from the early stages of the project.

Once the interface design is established, front-end development will proceed alongside the backend implementation.

Development will focus on responsive behaviour, data-heavy interfaces, interaction patterns and the practical usability of the platform across its different user types.

Deliverables

Functional web application on staging environment.

Mid-November 2026

Testing & Launch

Included within the overall project timeline

The completed platform will be tested across its core workflows and relevant devices before launch. A staging environment will be used for review and User Acceptance Testing.

Following completion of testing and agreed fixes, the platform will be prepared for production deployment and launch.

Deliverables

Tested production-ready web application.

UAT

The project includes up to 2 consolidated rounds of UAT feedback and fixes during the staging phase. Bugs are limited to deviations from the approved designs or agreed functionality. New features, enhancements or changes in scope will be treated separately.

03 / The Platform

The Platform

The proposed ConnectX platform is built around four connected experiences: the customer organising an event, vendors providing event services, venue owners managing their properties, and ConnectX operating the ecosystem between them.

The four experiences are connected through a common planning, enquiry, availability and negotiation system.

01

Customer Experience

The proposed platform gives customers a central place to define their event requirements, discover suitable vendors and venues, manage enquiries and track their planning progress.

  • Create an event and define its key details.
  • Break the event into individual sub-events, functions or ceremonies.
  • Define requirements such as budget, location, event type, preferred style and other relevant preferences.
  • Search for vendors based on their specific requirements.
  • View only vendors whose profile, specialisation and availability are relevant to those requirements.
  • Explore vendor profiles, portfolios and relevant information.
  • Enquire with vendors and receive proposals.
  • Participate in proposal and negotiation workflows.
  • Track vendors and services that have been shortlisted or finalised.
  • Monitor the overall progress of their event.
  • Receive relevant notifications throughout the planning process.

The same principle applies to venue discovery. Customers can specify requirements such as destination, event dates, expected requirements, budget and property preferences, allowing the platform to surface relevant available venues rather than presenting an unrestricted list of properties.

The proposed customer experience therefore moves beyond simple vendor browsing. It establishes the foundation for progressively more relevant matching and recommendations as the platform evolves.

02

Vendor Experience

The proposed platform will give vendors a structured environment to present their services, define their specialisations and manage their availability.

  • Maintain a structured vendor profile.
  • Define their services and areas of specialisation.
  • Specify category-specific attributes. For example, photographers may identify their preferred photography styles.
  • Manage availability by blocking dates on their calendar.
  • Receive enquiries based on relevant event and service requirements.
  • Review customer and sub-event requirements.
  • Respond with proposals.
  • Participate in proposal and negotiation workflows.
  • Receive relevant notifications.
  • Track the status of their customer interactions.

Vendor information will actively contribute to the matching process. Specialisation, availability, location, budget suitability and other relevant attributes can influence which vendors are surfaced to a customer.

03

Venue Owner Experience

Venue booking will be treated as a dedicated module within the platform.

Although venues form part of the wider vendor ecosystem, the nature of venue enquiries and negotiations makes them sufficiently different to warrant a dedicated experience.

The proposed venue module will focus particularly on properties relevant to destination weddings and other high-value events, including luxury hotels, five-star properties, heritage properties and other specialised venues.

  • Maintain a structured property profile.
  • Present property information, imagery, facilities and relevant event capabilities.
  • Define the types of events and functions the property can accommodate.
  • Manage relevant availability.
  • Receive enquiries based on customer event requirements.
  • Review event dates, requirements and sub-event information.
  • Respond to venue enquiries.
  • Submit proposals and commercial responses.
  • Participate in negotiation workflows.
  • Receive notifications and track the status of active enquiries.

Unlike a conventional hotel booking platform, the proposed venue workflow is centred around enquiry, proposal and negotiation, rather than instant booking.

This is particularly relevant for destination weddings, where venue selection can involve multiple functions, dates, accommodation requirements, property-specific considerations and commercial negotiations.

04

ConnectX Operations

ConnectX will have a central operational layer connecting customers, vendors and venue owners.

The proposed administration interface will allow ConnectX to:

  • Manage and oversee customers, vendors and venue owners.
  • View event, sub-event, vendor and venue information.
  • Monitor enquiries, proposals and negotiations.
  • Participate in or mediate customer, vendor and venue interactions.
  • Track event and booking progress.
  • Manage relevant platform data and workflows.
  • Intervene when a customer requires assistance.
  • Coordinate venue enquiries and negotiations where required.
  • Support hybrid or offline workflows where ConnectX becomes directly involved in delivering or coordinating a service.

This operational layer is particularly important for venue booking, where ConnectX may need to facilitate communication and negotiation between the customer and property rather than simply allowing the two parties to transact independently.

System overview

The connected ecosystem

Operational layerConnectX Operations

Coordinates & facilitates

01Customer

Plans & discovers

ConnectXEvent planning & vendor ecosystem
02Vendor

Offers & responds

03Venue Owner

Properties & negotiations

04 / Phase One Boundaries

Phase One Boundaries

Phase One is proposed as the foundation of the ConnectX platform. The system will be structured with future expansion in mind. Any subsequent phase or additional functionality will be scoped and commercialised separately.

  1. 01

    Financial transactions are proposed to remain outside the platform during Phase One. The platform will support vendor discovery, enquiries, proposals and negotiations, but will not process or accept payments from users in this phase.

  2. 02

    Proposal and negotiation workflows are included within the initial platform concept.

  3. 03

    Future hybrid or fully offline ConnectX-managed workflows can be supported through later phases.

  4. 04

    AI-assisted functionality is reserved for a future phase and is not included in the current Phase One implementation.

  5. 05

    Advanced operational workflows and additional automation can be scoped separately as the product evolves.

05 / Proposed Tech Stack

Proposed Tech Stack

  1. 01Laravel
  2. 02Filament
  3. 03Livewire
  4. 04Alpine JS
  5. 05MYSQL
06 / Pricing & Milestones

Pricing & Milestones

The total proposed price for Phase One of this project is ₹10,00,000 + GST.

The proposed payment structure consists of three milestones.

Payment milestones
MilestoneTimelinePayment
Initiation31st August 2026₹3,30,000 (33%)
Design Sign-offDesign completion / mid-project₹3,30,000 (33%)
Project Go-liveMid-November 2026₹3,40,000 (34%)
07 / Support & Maintenance

Support & Maintenance

  1. 01

    The initial post-launch support period will cover bug fixes relating to the delivered Phase One functionality for one month after go-live.

  2. 02

    A bug is understood as a deviation from the approved design or agreed functionality, rather than a new feature or enhancement.

  3. 03

    New functionality, additional modules, significant workflow changes or enhancements requested after delivery will be scoped separately.

  4. 04

    ArtWorksIT proposes to recommend, configure and manage the hosting infrastructure based on the platform's load, requirements and assets. The appropriate server environment will be assessed as part of the implementation.

08 / Terms & Assumptions

Terms & Assumptions

01Project Deliverables & Code Ownership

ArtWorksIT assures that all code and design components created for the Client's platform are original and tailored to the project's requirements. Code and documentation will be versioned and securely managed through GitHub, providing Client access to code versions and updates as needed. Upon full payment, the Client will have ownership of the custom website or application code, design files and project-specific deliverables created by ArtWorksIT, excluding third-party software, libraries, frameworks, fonts, plugins, stock assets and other components subject to their respective licences. ArtWorksIT reserves the right to showcase the completed project in its portfolio and marketing materials unless otherwise agreed upon in writing.

02Confidentiality & Data Security

Both parties agree to keep all shared information confidential and will not disclose it to third parties without prior written consent. This provision will remain effective after the project's completion.

03Client Responsibilities & Project Scope

The Client is responsible for providing all necessary project details, business rules, content, vendor information and timely feedback required for the project. The Client will provide timely access to relevant stakeholders for product decisions, approvals and clarification of workflows. Delays in requirements, content, approvals, feedback or other Client dependencies may result in corresponding changes to the project timeline.

04Payment Terms & Financial Conditions

All payments are due Net 7 days from the invoice date, and all prices are exclusive of GST. The total project fee excludes costs for external services that may be required. Work will begin once the initial payment is received. If there are delays in payments, work may be paused temporarily and resumed once outstanding payments are cleared. The platform will be scheduled for go-live upon receipt of the applicable go-live stage payment.

05Termination, Dispute Resolution & Governing Law

Either party may terminate the agreement in the event of a material breach by providing written notice. If terminated, Client agrees to compensate ArtWorksIT for services rendered and any applicable expenses. Disputes will first be addressed through good-faith negotiations. If unresolved, both parties consent to submit to the exclusive jurisdiction of the courts in Bangalore. This Agreement is governed by and construed under the laws of India, with Bangalore courts having exclusive jurisdiction.

06Modifications & Entire Agreement

This document contains the full understanding between the parties and supersedes previous agreements. Any modifications must be in writing and signed by both parties.

07Assumptions

The Client is responsible for providing the final requirements, business rules, content guidelines and necessary assets. Data entry and migration of extensive vendor or event data will be the responsibility of the Client unless specifically included in the scope. Hosting and infrastructure management will be defined as part of the final implementation and commercial arrangement. The platform will be developed in phases, and functionality not explicitly included in Phase One will be considered for subsequent phases.

ArtWorksIT
ArtWorksITartworksit.com

Proposal

Proposed Wedding & Corporate Event Planning Platform