<[xFlux]>

  • Technical Specifications

    Technical Specifications

    It is time to organize the technical specifications that I have been thinking about and planning. The frontend is pretty simple at this stage. The backend will probably be written in Python or Node. Additionally, at least three external services will be required for a fully working product. 1. Application Architecture Framework & Runtime: Database:…

  • High Fidelity Wireframe V1

    High Fidelity Wireframe V1

    Profile & Portfolio Wireframe(for talent) This provides a developer’s look at the “Portfolio & Profile” wireframe, explaining what I am building and why. 1. Purpose-Driven Design: Maximizing Match Accuracy The foundation of my platform is the belief that accurate data leads to superior outcomes. I’ve designed the profile to act as a precision filter for…

  • UX: Lost in vetting process

    UX: Lost in vetting process

    The second most difficult issue was how the client starts work with the chosen candidate. I can simply follow the industry leader’s steps, but I do not think Upwork’s Client-to-Work process is really user-friendly or efficient. This is a topic for the next post. The table above shows the steps of Upwork’s Client-to-Work process. As…

  • Low Fidelity Wireframe V1

    Low Fidelity Wireframe V1

    Based on the sitemap, I created low-fidelity (LF) wireframes for both the Talent and Client user groups. The most important goal during the LF wireframing is to establish a good process to identify what I do not know. If I can draw a wireframe with the proper basic information architecture in ten minutes, then this…

  • 9 UX Problems

    9 UX Problems

    It is surprising to realize there have been so many good matching products available for a long time, but they still suffer from significant UX problems that prevent users from ever becoming familiar with them. Two user groups – talent and client means more UX problems to resolve. Most public UX and conversion studies suggest…

  • Sitemap V2 & The first UX problem

    Sitemap V2 & The first UX problem

    The initial benchmarking indicates there are about 24 high-level pages. Subpages are not included yet, but the total page count for most web products is typically around 40, and this site will nearly hit that 40-page average. The membership process and the Client-to-Talent payment process will require at least five pages each, and creating a…

  • Benchmarking V1

    Benchmarking V1

    Kay points: cheaper, simpler, fast vetting process, narrower target Feature Lemon.io Upwork Twine.net Primary Focus Vetted Software Developers (primarily for startups and MVPs). The world’s largest General Freelance Marketplace (covering all skills). Vetted creative and tech freelancers (covers thousands of skills). Talent Pool Size & Vetting Small, highly vetted pool (only approx 3-5% of applicants…

  • Sitemap V1

    Sitemap V1

    The site will have two user groups – talent and client. Time to time, they can possibly switch the user categries. I think the rate of staying on same user group when they create an account, is pretty high. Rarely, they will switch the group. It is a little unclear how to build the page…

  • Product Idea: simpler, LLM driven talent/client matching

    1. Client/Talent registration needs to be as simple as possible.  2. Clients do not need points, talent needs proposal points to apply for jobs.  3. Talent gets proposal points by providing proof of careers. With the proposal point, talents can apply to jobs. 4. Grant 1 point per week once the talent login to the…

  • Billing Management System

    Billing Management System

    Overview A comprehensive web platform that automates the end-to-end billing workflow for managing 47+ external collaborators—from time tracking to invoice processing. The system integrates with Teamwork and Google Sheets, using AI agents to reduce manual work by 80%+. The Problem Project managers spent 10-15 hours monthly on manual tasks: Result: Missed deadlines, payment delays, and…