phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

AI Council Information Platform Frontend MVP (React / Next.js)

  • Posted:
  • Proposals: 44
  • Remote
  • #4497139
  • OPPORTUNITY
  • Open for Proposals
Huzaifa M.Abeselom S.Safeer H.Imran K.Awais A. + 39 others have already sent a proposal.
  • 4

Description

Experience Level: Entry
We are seeking an experienced React / Next.js frontend developer to build the frontend MVP for an AI-powered local council information platform called myClerk.

The backend API already exists and includes endpoints for:

council listings
user identity
chatbot querying
documents and sources

The provider will build the frontend only.

Scope includes:

Public homepage using supplied branding concepts
SEO metadata integration
User registration/login system
Email verification
Council dropdown selection during registration
User account/settings page
Chatbot interface connected to API
Citation/source display
Responsive UI
GitHub delivery and documentation

Preferred stack:

React or Next.js
TypeScript preferred
Tailwind or similar modern UI framework

The supplied branding concepts must be closely followed.

Important:
All bidders MUST clearly state that their quote is their FULL AND FINAL FIXED PRICE for delivery of the complete MVP described.

Please include:

Estimated completion timeframe
Relevant examples of previous work
Experience with authentication systems and API integrations
Confirmation that you can deliver deployable production-ready code

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • VCONN P.

    Hi Robert,

    Thanks for the invite.

    A few questions before we provide an accurate quote:

    1. Are finalized Figma/UI files available, or only branding concept references?

    2. Will the backend already manage email verification and password reset token generation?

    3. Can you provide sample API responses for chatbot answers and citations?

    4. Which authentication mechanism is being used (JWT, cookies, OAuth, etc.)?

    5. Should chat history persist server-side or only during active sessions?

    6. Are there accessibility/WCAG requirements for UK council compliance?

    7. What VPS/deployment environment is planned for production?

    8. What duration of post-launch support do you expect?

    We would be happy to discuss the project further.

  • Shobi K.


    A few quick questions:
    1. Will final Figma/UI screens be provided, or only branding references?
    2. Is the email verification flow already fully handled from the backend side?
    3. Should chat history remain only for active session, or do you plan to store conversations permanently later?