Streamline PostgreSQL Projects with Vollna

About Akerio. Akerio is a UK-based applied AI company. We build platforms that turn messy enterprise data into scored, auditable recommendations: the next diesel price for one of Europe's largest independent fuel distributors, a risk flag on a tenant across 41 shopping centres, a credit score a bank's committee can trace back to the source record. Our models are built by a PhD team from Stanford and the University of Chicago, every output shows what drove it and how confident it is, and the platform runs on-premise or in the cloud. We are live in production across energy, commercial real estate and financial services, with 18 AI modules running in one deployment alone. We are a small team shipping to demanding enterprise clients, so the work you do reaches production and gets used.
• Job: Full time
• Job type: Remote

The role
Our clients do not buy a model. They buy a better decision: which lease to renegotiate this quarter, which tenant is about to pay late, how much footfall a mall will see next month. On our retail property platform, revenue, footfall, tenant risk and mall performance models already run every month through Airflow across 41 shopping centres. The next phase adds collections and cash projections, campaign ROI, and models trained per client. You own that model portfolio: accuracy, explainability, retraining, and the step from "runs on one client's data" to "runs for every client". You work with our Chief AI Engineer and directly with the client's asset, leasing and finance teams.
What you will work on
• Forecasting: tenant turnover, hourly footfall per location over a 12-month horizon, energy use, collections and cash flow.
• Risk scoring: tenant payment-delay risk, brand risk scores, early warnings on underperforming units.
• Lease analytics: estimated rental value (ERV) and which contracts sit below market.
• Explainability: every output ships with drivers (SHAP) and a confidence range a leasing manager can understand.
• MLOps: moving from scheduled scripts to proper experiment tracking, a model registry and per-client training, with clear accuracy reporting back to the product.
• LLM quality: the AI assistant answers questions over these numbers with 53 tools. You help design its evaluation: test sets, terminology rules, and the Langfuse feedback loop.
Beyond real estate, the same skills apply to our energy pricing and banking risk work, so you will see more than one industry.
Our stack
Area What we use
Modelling Python, pandas, scikit-learn, XGBoost, Prophet and other time-series methods
Explainability SHAP
Orchestration and serving Apache Airflow for monthly training and scoring runs, FastAPI compute service, MLflow being introduced
Data PostgreSQL and PostGIS, Excel and ERP exports from client systems
LLM Anthropic Claude via API, RAG over client data, tool calling and MCP, Langfuse for conversation and quality monitoring
Infra Azure, Docker, Jenkins, Bitbucket
How we build Jira, spec-first work with AI coding tools (Claude Code), code review on every PR
Your first six months
• First month: you know one live model inside out (data, features, metrics, failure modes) and ship one measurable improvement to it.
• Month three: you own a model family (for example tenant risk) including retraining, monitoring and the accuracy numbers clients see.
• Month six: you lead the modelling side of a new client rollout or new module, from use-case scoping to an advisory-mode pilot, and mentor a junior.
What you bring
• 5+ years building ML models that ran in production and changed real decisions, not only research or dashboards.
• An MSc or PhD in a quantitative field (statistics, computer science, economics, operations research), or equivalent depth.
• Strong time-series forecasting, plus at least one of: risk or default scoring, demand forecasting, pricing.
• Sound statistics: you know when a backtest lies, how to handle sparse or messy client data, and how to explain uncertainty to a CFO.
• Production Python: clean, tested, reviewable code an engineer can deploy without rewriting it.
• Experience putting models on a schedule (Airflow or similar) and tracking them (MLflow or similar).
• Fluent written and spoken English.
Nice to have
• Retail, shopping centre, real estate or energy data.
• LLM evaluation in production: test sets, LLM-as-judge, failure analysis from real user sessions.
• Geospatial data or footfall and sensor data.
• Multi-tenant model training: one pipeline, many clients, different data quality.
• Turkish, helpful for working with current client teams.
How we work
Every model starts in advisory mode next to the client's current process and earns trust by beating it on agreed metrics. You present results to client teams yourself, so you hear quickly whether a model helps.
Hiring process
10. 30-minute intro call.
11. 30-minute session: present your case to the CPO and an engineer.
12. 15-minute call with a founder.
What we offer
• Fully remote, with overlap on UK and Türkiye working hours.
• Models in production with real outcome data coming back every month.
• A PhD-heavy AI team to think with.

About Akerio. Akerio is a UK-based applied AI company. We build platforms that turn messy enterprise data into scored, auditable recommendations: the next diesel price for one of Europe's largest independent fuel distributors, a risk flag on a tenant across 41 shopping centres, a credit score a bank's committee can trace back to the source record. Our models are built by a PhD team from Stanford and the University of Chicago, every output shows what drove it and how confident it is, and the platform runs on-premise or in the cloud. We are live in production across energy, commercial real estate and financial services, with 18 AI modules running in one deployment alone. We are a small team shipping to demanding enterprise clients, so the work you do reaches production and gets used.
• Job: Full time
• Job type: Remote

The role
Our retail property analytics platform, live across 41 shopping centres, runs on a set of NestJS microservices: a core business service, an AI service that calls LLM tools, a notification service, and a Python compute service that serves forecasts and risk scores. Every month Airflow retrains and reruns revenue, footfall, tenant risk and mall performance models, and the backend has to get those results to the screen fast and correctly. You join the team that builds and runs these services. You will write production code from your first month, with a senior reviewer on every pull request.
What you will work on
• NestJS endpoints for leasing, finance, visitor and budget modules: DTOs, validation, permissions, and the SQL behind them.
• PostgreSQL and PostGIS: schema changes, migrations, query tuning, statement timeouts on heavy reports.
• Service-to-service work over gRPC and Kafka, Redis caching, and real-time updates over Socket.IO.
• Endpoints that Airflow calls to run forecasts and write back results and accuracy metrics.
• The AI service: tool definitions the LLM can call, MCP integration, caching AI commentary, logging every conversation to Langfuse.
• Python FastAPI work in the compute service when a model needs a new input or output.
• Production hygiene: health endpoints, log rotation, monitoring alerts, dependency and security upgrades flagged by Trivy.
Our stack
Area What we use
Services Node.js, TypeScript, NestJS, Yarn workspace monorepo, gRPC, Kafka, Redis, OpenSearch, Socket.IO
Compute Python, FastAPI, pandas, scikit-learn
Data PostgreSQL 17, PostGIS, SQL migrations
Scheduling Apache Airflow
AI Anthropic Claude via API, tool calling, MCP, Langfuse
Infra Azure, Docker and Docker Compose, nginx, pm2, Jenkins, Bitbucket, OpenTelemetry and Jaeger, Trivy
How we build Jira, spec-first work with AI coding tools (Claude Code), code review on every PR
Your first six months
• First month: environment running, first fix merged in week one, then one endpoint shipped with tests.
• Month three: you own a module's backend (for example finance or budget) and its test suite.
• Month six: you take a feature from spec to production with light review and handle its production issues.
What you bring
Junior (0 to 2 years):
• A computer science or engineering degree, or equivalent proof that you can build software.
• TypeScript or JavaScript you have used on something real: an internship, a serious side project, open source. Node.js is a big plus.
• SQL beyond SELECT: joins, indexes, transactions.
• Git, the command line, and the habit of reading the docs before asking.
Mid (2 to 4 years):
• Production backend experience in Node.js and TypeScript, ideally NestJS.
• You have designed REST APIs and PostgreSQL schemas other people built on, and written migrations that ran on live data.
• Testing as a habit: unit and integration tests with Jest or similar.
• Docker, CI pipelines, and you have debugged a service in a deployed environment.
Both levels: clear written English, curiosity about how the data is used, and comfort with AI coding tools while still owning every line you merge. Turkish is a plus.
Nice to have
• Python and FastAPI.
• Kafka, gRPC, Redis or any event-driven microservice work.
• PostGIS or other geospatial data.
• Exposure to LLM APIs, tool calling or MCP.
• Azure, Linux server administration or monitoring setup.
How we work
Spec before code, code review on every pull request, and a Jira board fed by real client feedback every week. Juniors pair with a senior every week.
Hiring process
4. 30-minute intro call.
5. 30-minute session: present your case to the CPO and an engineer.
6. 15-minute call with a founder.
What we offer
• Fully remote, with overlap on UK and Türkiye working hours.

Location: Remote (Montreal-based preferred)
Type: Freelance, Part-Time (Long-Term)

About MageMontreal
MageMontreal is a Montreal-based eCommerce agency and certified partner of Adobe Commerce (Magento), Shopify, BigCommerce, and WooCommerce. We build and maintain complex B2B and B2C commerce platforms for clients across Canada and the US.

The Role
We're looking for an experienced Senior Odoo Solution Architect / Technical-Functional Consultant with 8+ years of hands-on Odoo experience to support and evolve our live Odoo 19 environment. This is not a purely development-focused role. We need someone who can independently lead client discussions, understand business requirements, design ERP solutions, recommend best practices, and take ownership of implementations. You'll work closely with our COO, Project Manager, and stakeholders as a trusted Odoo advisor while remaining hands-on with technical solutions.

Key Responsibilities
- Lead discovery sessions, gather requirements, and analyze business processes.
- Design scalable Odoo solutions and translate business needs into functional and technical specifications.
- Advise stakeholders on ERP architecture, workflows, integrations, and best practices.
- Own Odoo implementations from solution design through deployment.
- Maintain and enhance our live Odoo 19 instance, including upgrades, bug fixes, and custom modules.
- Develop Python customizations and REST/JSON-RPC API integrations.
- Integrate Odoo with Confluence, Microsoft Teams, Outlook, Bitbucket, and other business tools.
- Support AI-powered automation using LLM APIs and MCP integrations.
- Document solutions, architecture decisions, and workflows in Confluence.

Must-Have Requirements
- 8+ years of direct, hands-on Odoo experience.
- Proven experience as an Odoo Solution Architect, Senior Odoo Consultant, or Technical-Functional Consultant.
- Strong client-facing consulting experience, including discovery sessions, requirements gathering, and solution design.
- Experience leading end-to-end Odoo ERP implementations.
- Hands-on experience with Odoo 17, 18, or 19.
- Strong Python, Odoo ORM, custom modules, and PostgreSQL knowledge.
- Experience with REST/JSON-RPC APIs, integrations, and Git.
- Ability to independently recommend and implement technical solutions.
- Strong spoken and written English for direct client communication.
- Comfortable working autonomously in a remote, async-first environment.

Nice to Have
- Experience with Odoo implementation partners or multiple clients.
- French language proficiency.
- eCommerce experience (Shopify, Magento, etc.).
- AI-assisted development tools (Claude, Cursor, Copilot).
- Familiarity with LLM APIs, MCP, and workflow automation (n8n, Make, Zapier).
- JavaScript / OWL experience.

We're looking for a senior Odoo expert who can independently consult with clients, design solutions, and take ownership of complex ERP projects.

About Akerio. Akerio is a UK-based applied AI company. We build platforms that turn messy enterprise data into scored, auditable recommendations: the next diesel price for one of Europe's largest independent fuel distributors, a risk flag on a tenant across 41 shopping centres, a credit score a bank's committee can trace back to the source record. Our models are built by a PhD team from Stanford and the University of Chicago, every output shows what drove it and how confident it is, and the platform runs on-premise or in the cloud. We are live in production across energy, commercial real estate and financial services, with 18 AI modules running in one deployment alone. We are a small team shipping to demanding enterprise clients, so the work you do reaches production and gets used.

• Job: Full time
• Job type: Remote

The role
Our largest deployment, a retail property analytics platform, is live across 41 shopping centres. Asset managers, leasing and finance teams open it to see footfall, turnover forecasts, tenant risk and NOI, then ask the built-in AI assistant why a number moved. Behind it sit 49 dashboard widgets, 53 AI tools, a set of NestJS microservices and a Python compute service. You take features across that whole path: the React screen, the NestJS endpoint, the Postgres query, and the AI commentary that explains the result. You will also talk to the people using it, because most of our backlog comes straight from their feedback.

What you will work on
• Dashboard widgets for leasing, finance and visitor analytics: time-series charts, forecast versus actual, filters that live in the URL so a view can be shared.
• The customizable home dashboard: drag, resize and save widget layouts per user.
• NestJS microservices: core business APIs, notifications, and the AI service that runs LLM tool calls and talks to our tools over MCP.
• Data endpoints over PostgreSQL and PostGIS, with SQL migrations you write and own.
• Wiring Python forecasting and risk models (FastAPI compute service, scheduled by Airflow) into the product.
• AI features in the UI: chat, quick summaries and per-widget AI commentary, cached in Redis and generated in the user's language.
• Production quality: health checks, logging, dependency upgrades, and closing security findings before they become incidents.

Our stack

Frontend: React, TypeScript, Vite, MUI, Tailwind, shadcn/ui, Zustand, React Router, ApexCharts, React Grid Layout, i18n (Turkish and English)

Backend: Node.js, NestJS microservices in a Yarn workspace monorepo, gRPC, Kafka, Redis, OpenSearch, Socket.IO

Data: PostgreSQL 17 with PostGIS, SQL migrations
Compute and ML Python, FastAPI, Airflow for scheduled forecast and scoring runs

AI: Anthropic Claude via API, tool calling and MCP, RAG over client data, Langfuse for monitoring conversations and quality

Infra: Azure, Docker and Docker Compose, nginx, Jenkins, Bitbucket, OpenTelemetry and Jaeger, Trivy; Kubernetes (Rancher) on the roadmap

How we build: Jira, Figma, spec-first work with AI coding tools (Claude Code), code review on every PR
You need to be strong in TypeScript on both sides. The rest you can pick up here.

Your first six months
• First month: local setup running, first pull request merged in week one, one widget or endpoint shipped to production.
• Month three: you own one product area end to end (for example finance analytics) from Figma to production.
• Month six: you shape API and frontend standards across services and pair with juniors on their first features.

What you bring
• 4+ years building production web applications, with real depth in TypeScript, React and Node.js.
• NestJS or a similar structured Node framework, REST API design, and PostgreSQL schema and query work.
• You have shipped data-heavy UIs: charts, big tables, filters, exports, and you know how to keep them fast.
• Docker, CI pipelines and debugging in a deployed environment, not only on localhost.
• You write tests and care about code that the next person can read.
• Clear written English. Turkish is a plus: most of our current users work in Turkish.
Nice to have
• Python and FastAPI, enough to read and extend a compute endpoint.
• Microservice plumbing: Kafka, gRPC, Redis caching, tracing.
• You have built a UI on top of LLM output: streaming, citations, tool calls, human review.
• Experience with real estate, retail, energy or finance products.

How we work
Small team, short feedback loops. Client feedback lands in Jira every week, we write the spec before the code, and every pull request gets a review. We use AI coding tools as standard and still expect you to own every line you merge.

Hiring process
1. 30-minute intro call.
2. 30-minute session: present your case to the CPO and an engineer.
3. 15-minute call with a founder.

What we offer
• Fully remote, with overlap on UK and Türkiye working hours.

GATELESS Music is redefining how music gets made. We're a vertical SaaS platform built for artists, producers, and music professionals to connect directly through unreleased production — without the gatekeepers.
We’re looking for a seasoned FULL Stack Developer to lead our engineering team as we scale. If you’ve got deep technical chops, strong leadership instincts, and a background in music production — we want to hear from you.
Responsibilities:
* Lead and manage cross-functional dev teams to execute key technical deliverables on time and within scope
* Translate product requirements into detailed technical tasks and sprints
* Oversee progress on both frontend and backend development
* Maintain alignment between product vision and tech implementation
* Manage and communicate with contractors across time zones
* Identify roadblocks early and remove them before they impact the team
* Ensure best practices around version control, QA, security, and deployment
* Collaborate directly with the founder to help scale our infrastructure and roadmap
Experience:
* 5+ years of experience managing technical teams and web-based software projects
* Proven experience working with Node.js (Express), Next.js, Nuxt.js, PostgreSQL, AWS, Stripe, and SendGrid
* Ability to manage multiple timelines and priorities in a fast-moving startup
* Strong communication, documentation, and sprint planning skills
* Previous success managing remote teams and scaling systems across cloud infrastructure
* Bonus: Background in music production or music tech



Please send an introduction and how much experience you have for the following:
Node.js (Express), Next.js, Nuxt.js, PostgreSQL, AWS, Stripe, and SendGrid

## Senior Full-Stack Developer / Technical Lead – SaaS Product Development

We are looking for an experienced Senior Full-Stack Developer / Technical Lead to help design, architect, and develop a new B2B SaaS product from the ground up.

This is an early-stage software development project with a defined product concept and requirements.

We are seeking a hands-on developer who can take ownership of technical architecture, contribute directly to development, and help establish a strong foundation for future scalability.

### Required Skills
- Proven experience developing SaaS products from scratch
- Strong full-stack development experience
- React / Next.js, Node.js, TypeScript
- PostgreSQL and database architecture
- Cloud infrastructure (AWS or similar)
- API development and third-party integrations
- Authentication, security, and multi-tenant architecture
- Experience leading technical development projects

### What We're Looking For
- An experienced, independent developer, not an agency
- Strong architectural and problem-solving capabilities
- Ability to work independently and collaborate with additional developers
- Clear communication and reliable delivery
- Experience taking SaaS products from concept to production

### Project Details
- Remote collaboration
- Flexible, milestone-based engagement
- Potential for long-term cooperation
- Full project specifications shared privately with shortlisted candidates

### To Apply

Please provide:

1. Examples of SaaS products you have personally developed.
2. Your experience as a technical lead or software architect.
3. Your preferred technology stack and why.
4. Your hourly rate and weekly availability.
5. Your experience working on early-stage software products.

We are looking for a reliable technical partner who can contribute to building a high-quality, scalable software product.

We've built a rental listings web app. The web app (Next.js) and the backend API (Node/Express) were built largely with AI coding tools. The features work, but the code needs an experienced engineer to review it and make it production-ready before launch.

This is not a build-from-scratch job. You'll audit the existing code, report what's risky, and fix the most important issues.

*Tech stack*
- Frontend: Next.js 14 (App Router), TypeScript, Tailwind CSS
- Backend: Node.js, Express, TypeScript, Zod
- Supabase: Postgres, Auth (Google OAuth and email), Storage, Row Level Security
- Sharp for image processing; Vercel for the web app
- Separate repos for web and API

*What's built*
- Landing page; listings search with filters and SEO routes; property detail with contact-owner reveal
- Google and email authentication, with renter and landlord roles
- Five-step property listing form with photo upload
- Landlord dashboard (listings, leads, saved properties, profile)
- REST API for all of the above, plus a listing auto-expiry job

*Scope*

Phase 1: Audit (deliver a written report)
Review both repos and produce a prioritised list of issues (critical, high, medium), covering:
- Security: Supabase RLS policies, auth middleware and JWT verification, authorization on every landlord endpoint, input validation, secrets and environment handling, CORS, rate limiting on auth and contact reveal
- Data integrity: schema, constraints, indexes for search queries, migrations
- Error handling and logging on the API
- Next.js: server/client component boundaries, caching, SEO metadata, image optimisation, and anything broken in production builds
- Dead code, duplicated logic, and inconsistent patterns typical of AI-generated code

Phase 2: Fix
Fix every critical issue and as many high-priority issues as the budget allows, in order of priority. Document anything you don't get to.

Phase 3: Production readiness
- Make sure both apps build and deploy cleanly, with production environment configs
- Add basic error monitoring (e.g. Sentry) and health checks on the API
- Write a short launch checklist with remaining risks

*What we're looking for*
- Senior-level full stack experience with Next.js and Node/Express in production
- Strong Supabase knowledge, especially RLS and Auth
- A security-minded reviewer who can judge what really matters before launch versus what can wait

*Use of AI tools*
We encourage using AI-assisted tools like Claude Code, Cursor, or Copilot. The codebase was built with them, and using them well will help you move faster within the budget. That said, AI output needs careful checking, and that's exactly why we're hiring a human expert:
- You must understand and review every change you submit. Don't merge AI-generated fixes you haven't verified.
- Test security and auth changes manually, not just by trusting the generated code.
- Each PR description should explain what changed and why, in your own words.
- Tell us which tools you use and how you use them in your workflow.

*Deliverables*
- Audit report (Markdown or Google Doc)
- Fixes as pull requests with clear descriptions
- Launch checklist and a list of remaining issues

*Budget and engagement*
- $500 fixed, in two milestones: $150 for the audit report, $350 for the fixes and production-readiness work
- Expected effort: about 20–30 hours
- Timeline: 1–2 weeks

*To apply, answer these:*
1. Describe a codebase you've audited or hardened for production. What were the most serious issues you found?
2. In a Supabase + Express app, what are the first three things you'd check for security?
3. Have you worked with Supabase RLS and Auth in production?
4. Your availability over the next two weeks.
5. Which AI coding tools do you use, and how do you check their output before shipping it?

Start your proposal with the word "Verified" so we know you read this far.

Software Architecture & AI Automation Planning — Event Booking Platform

We got client an event management and marketing agency planning a centralized, multi-tenant
booking platform for our clients.

We are looking for a software architect or product engineering team to help us define the MVP,
design the architecture, assess automation and integration feasibility, and prepare a practical
implementation roadmap.
The initial engagement is paid discovery, architecture and feasibility.
Subsequent development phases require separate scope and budget approval.
Product Background
The platform will support concerts, conferences, corporate events, brand activations,
workshops, dining experiences and other reservation-based activities.
Individual clients should have branded booking experiences, while the agency centrally
manages events, availability, promotions, payments and customer communications.
The planned platform includes:
● Client and event management: Multiple brands, venues, events and locations, with
staff permissions and client-specific reporting.
● Web application: Event discovery, registration, ticket selection, checkout and
booking management.
● Conversational channels: Chatbot, WhatsApp and voice-assisted enquiries and
bookings, with human handoff.
● Unified inventory: Consistent availability across channels, temporary holds, hold
expiry and safeguards against overbooking.
● Native promotions: Early-bird offers, coupons, bundles, group offers, eligibility rules
and redemption quotas.
● Payments: Payment synchronization, refunds and transaction reconciliation.
● Business integrations: Selected CRM, POS, marketing and communication
systems, subject to feasibility and API access.
● Internal tools: An administration dashboard for bookings, customer support,
operations and reporting.
The native booking and promotions engines should remain authoritative for availability, eligibility
and quotas.
Phase 1 — Discovery, Architecture & Feasibility
The objective is to turn the product requirements into a prioritized, technically sound and
commercially realistic implementation plan.
Scope
Requirements and MVP definition
● Review the supplied PRS and clarify user journeys, operational requirements and
assumptions.
● Identify essential MVP functionality and features that should follow later.
● Define dependencies, exclusions and acceptance criteria.
Software architecture
● Design the multi-tenant application architecture, major components and data flows.
● Address tenant isolation, permissions, inventory consistency, reservation holds,
payment operations and auditability.
● Recommend the deployment approach, supporting services and operational
requirements.
Business process and workflow automation
● Design workflows covering enquiries, reservations, payments, confirmations,
reminders, modifications and cancellations.
● Define failure handling, retries, reconciliation and human intervention.
● Identify which processes should use deterministic rules and which may benefit from
AI.
AI and integration feasibility
● Assess chatbot, WhatsApp and voice requirements.
● Evaluate where LLM integration is appropriate, including knowledge sources,
permitted actions and human handoff.
● Define the API and webhook integration strategy.
● Identify provider dependencies, access requirements, operating costs and
unresolved feasibility questions.
Delivery and investment planning
● Prepare a prioritized backlog and phased implementation roadmap.
● Estimate development effort, resource requirements and indicative infrastructure and
third-party costs.
● Document risks, assumptions and decisions requiring stakeholder approval.
Deliverables
1. Updated PRS and prioritized MVP backlog.
2. Architecture and integration diagrams.
3. Booking and customer communication workflow designs.
4. AI feasibility assessment and recommended integration approach.
5. Indicative cost analysis and phased delivery plan.
6. Risk register and documented MVP acceptance criteria.
Phase 1 acceptance: The agreed documents are delivered, reviewed and updated to address
stakeholder feedback, providing sufficient clarity to decide whether to fund implementation.
Proposed Technical Direction
Our current preference is:
● Frontend: React and TypeScript.
● Backend: Node.js and TypeScript.
● Database: PostgreSQL.
● Cloud: AWS or Google Cloud.
● Supporting services: Redis and message queues where justified.
We welcome recommendations supported by delivery, maintainability and operating-cost
considerations.
The architecture should address security, automated testing, CI/CD, monitoring, backups and
recovery. Specific implementation targets will be agreed during discovery.
Potential Subsequent Phases
● Phase 2 — Full-Stack Web Application Development: Core booking MVP,
branded pages, administration tools, inventory, notifications and an initial payment
integration.
● Phase 3 — Offers, AI Integration & Workflow Automation: Native promotions,
conversational booking channels and selected CRM/POS integrations.
● Phase 4 — Scale & Marketplace: Advanced inventory and seating, event discovery,
analytics and broader integrations.
● Phase 5 — Continuous Improvement: Further automation, operational
improvements and expansion based on customer feedback.
These phases are an indicative roadmap. Each requires a separate scope, estimate, budget
approval and go/no-go decision.
Relevant Experience
We would value experience with:
● Software architecture and technical discovery.
● Multi-tenant platforms and full-stack development.
● Booking, inventory, payments or comparable transactional workflows.
● Business process automation and API integrations.
● AI integration with clear operational safeguards.
● Documentation and handover for ongoing development.
Please include relevant project examples, your proposed approach to Phase 1, an estimated
fee and fixed fee timeline, and your availability.
We are looking for experienced leaders.

We are looking for a developer specializing in EvolutionsGO (WhatsApp API in Go) and Supabase to urgently resolve a critical issue in QR Code generation in our healthcare SaaS system. The system currently uses EvolutionsGO to mirror and connect customers' WhatsApp, with the infrastructure running on Easypanel (Ubuntu Server / Traefik / Cloudflare Gray Cloud). Recently, the system stopped generating the QR Code on the SaaS screen for new connections, although the local databases (PostgreSQL and Redis) dedicated to the API are active and operating on Easypanel. The selected professional will be responsible for: 1. Analyzing EvolutionsGO logs in Easypanel to identify the cause of the failure in the connection route (/instance/connect or similar) that prevents the generation of the QR Code payload. 2. Clean up possible crashed/corrupted sessions or instances in local databases (Redis/Postgres). 3. Validate whether the current version of EvolutionsGO installed requires a compatibility update with the WhatsApp library (Baileys/Go). 4. Reestablish the complete connection flow, from clicking the SaaS button, through the call via Edge Function, to the successful generation of the QR Code and the status change to 'connected'. We offer full access to GitHub (source code), Easypanel (server) and Supabase (database). It is essential to have practical and direct experience with EvolutionsGO for this urgent fix.

Skills: Java, Linux, MySQL, Node.js, PostgreSQL, Redis, Cloudflare, Supabase

Project Overview

I'm looking for an experienced Senior Backend Developer to help investigate and resolve scaling issues in a digital asset custody wallet system.

Requirements

Strong backend development experience and knowledge of scalable system architecture.

Experience building and optimizing high-performance backend services.

Solid understanding of fintech systems and financial transaction processing.

Hands-on experience with double-entry ledger systems and maintaining financial data consistency.

Scope of Work

The initial task is to investigate the existing system, identify potential bottlenecks, and recommend or implement targeted fixes.

I'm looking for someone who can analyze the root cause of problems and propose practical, reliable solutions.

Budget: $20 for the initial task.

Please briefly describe your experience with digital wallets, financial ledgers, and backend scalability when submitting your proposal.

I need an experienced developer to complete a newsletter feature inside the existing admin dashboard of my live real estate website.

The application uses Replit, React/TypeScript, Express, PostgreSQL and Resend. Existing code and documentation are available for review; the feature is not yet fully tested or ready for production.

The work includes reviewing the existing implementation, completing consent and email confirmation, unsubscribe and suppression, campaign preview and approval, secure admin access, and protection against duplicate sending. Testing must use an independent environment with synthetic data and mock emails.

Please provide your relevant experience, a quote and timeline by stage, including any infrastructure costs. No changes to the live website, database, credentials or permissions, no deployment and no real emails without my separate approval.

Skills: JavaScript, Software Testing, Node.js, PostgreSQL, React.js, Typescript, Web Development, Backend Development, Frontend Development, Security

We are seeking an engineer who has personally built, modified, or maintained a Claude subscription-account integration gateway and operated a working solution. You must be able to demonstrate your contribution and results with existing test or operational evidence. General AI application development, API calls, or MCP usage alone is not sufficient.

We evaluate measured outcomes and practical engineering ability. We welcome different implementation approaches and do not require an identical past technology stack. Your solution must support our customer workflows and be compatible with our platform.

## Engagement Process

### 1. Review your existing experience and evidence

Describe a comparable system you personally worked on, a real stability issue you resolved, your changes, and the outcome. Provide existing redacted reports, logs, screenshots, or code evidence you are authorized to share. Include the running version, observation period, account/user scale, workload, measured reliability and latency, and known limitations. Clearly distinguish actual usage from simulations. No unpaid development or custom testing is required to apply.

### 2. Prepare a paid pilot in your environment

After agreeing the scope and fee, deploy your existing solution in an isolated environment you manage. We provide a domain. Use our base code as agreed, or a mutually approved compatible integration, focusing on Claude integration and account operational stability.

The pilot must include one-click configuration, one-click installation, and other agreed essentials needed for actual customer use. Adaptation, deployment, and support are paid work. New online-payment development is not required for the pilot; our team will manage test balances through the admin interface.

Preserve existing customer-facing features and business workflows. Any necessary changes require prior agreement on their purpose, impact, compatibility, and regression checks.

### 3. Test with real customers and retain complete data

After functional and readiness checks, we organize real customers to use one solution at a time. We cover Claude test-account and subscription costs, plus other direct testing expenses agreed in advance. Engineering fees are agreed separately.

We will agree on the observation period, workload records, acceptance metrics, and support arrangements before testing. Evaluation includes task completion and quality, reliability, latency, failures, known limitations, and actual costs.

All project-specific user data, test records, runtime logs, metrics, incident records, and analysis reports generated or lawfully collected during the pilot belong to us, subject to applicable user rights and privacy obligations. Retain them in full and provide client access and export for independent verification. Do not delete, overwrite, alter, or selectively withhold records without our written approval. Necessary corrections must preserve the originals, reasons, and audit trail.

### 4. Decide on code acquisition from the results

We decide whether to acquire the code only after reviewing complete real-customer test results. Purchase is not guaranteed. Agree the code price, transferable rights, third-party dependencies, temporary pilot-use license, and handover scope before the pilot. Open-source and third-party components remain subject to their licenses.

Payment for agreed pilot work does not depend on our decision to purchase the code or commission a later phase.

### 5. Integrate, deploy, and revalidate on our servers

If acquisition and the subsequent implementation scope are agreed, integrate the solution with our customized platform and deploy it on our servers. Revalidate existing workflows and stability with comparable workloads and metrics, documenting environment differences. Deliver the agreed source code, change notes, deployment and rollback documentation, and maintenance support.

## Existing Platform

Our team reports a customized platform based on open-source Sub2API v0.2.9, with existing improvements to log analysis, account and network operations, and Claude compatibility and stability. The reported environment is Go 1.27.3, PostgreSQL 18.6, and Redis 8.10.2; actual versions and configuration will be verified at kickoff.

These are compatibility requirements, not restrictions on your previous technology stack or proposed implementation. Alternative approaches are welcome when their compatibility, impact, and validation method are clear and mutually agreed. The pilot does not authorize unrelated feature changes or changes to our existing payment workflows.

## Terms and Application

Each phase will use a paid Upwork milestone with an agreed scope, schedule, fee, and acceptance criteria. Pre-contract communication and all freelancer payments remain on Upwork. Work must use authorized resources and comply with applicable provider terms.

Apply with a relevant project, your personal contribution, existing evidence, availability, and phase pricing. Do not share confidential client material or credentials.

## Screening Questions

1. Which Claude subscription integration gateway did you personally develop, modify, or maintain? Describe the access method, your contribution, and one real operational problem you resolved. Distinguish this from official API-only or MCP experience.
2. What existing evidence can you share for that solution's results? Include the running version, observation period, workload and scale, measured outcomes, and known limitations. Identify simulated results separately.
3. Can you provide a paid pilot in your environment with the agreed customer workflows and complete data access for us? State your availability, phase pricing, and principal dependencies. A free implementation plan is not required.

# Existing Airbnb Cleaning Management & Service Marketplace Software – Source Code Purchase

We are looking to purchase an **existing, fully developed vacation rental cleaning management and service marketplace platform**, including source code and commercial licensing rights.

**Our priority is to acquire an already developed and working software solution, rather than building a new application from scratch.**

We welcome proposals from software development companies, independent developers, and SaaS providers offering existing solutions or white-label platforms.

### Required Features

**1. Vacation Rental Calendar Integration**
- Airbnb calendar synchronization (Airbnb real authorized API).
- Booking.com and Vrbo integration preferred.
- Automatic cleaning task creation based on guest checkout dates.
- Multi-property calendar management.

**2. Cleaning Service Marketplace**
- Registration for property owners and cleaning professionals.
- Cleaner profiles, availability, pricing, and service areas.
- Job requests, offers, and booking management.
- Ratings and reviews.

**3. Automated Cleaning Operations**
- Automatic cleaning scheduling and task assignment.
- Cleaner notifications.
- Cleaning checklists and photo uploads.
- Job completion tracking.
- Property management dashboard.

**4. Payments and Administration**
- Stripe payment integration.
- Cleaner payouts and platform commissions.
- Admin dashboard.
- User and transaction management.

**5. Technical Requirements**
- Fully functional web platform.
- Mobile-responsive interface.
- Android and iOS applications preferred.
- Complete backend, database, and source code.
- Deployment documentation.
- White-label and commercial licensing rights.

### What We Are Looking For

We are particularly interested in:

- Existing SaaS platforms available for acquisition or licensing.
- White-label vacation rental management solutions.
- Previously developed Airbnb cleaning management applications that the seller has the legal right to license or sell.
- Working software requiring only limited customization.

### Information Required From Applicants

Please provide:

1. A live demo or video of your existing software.
2. A detailed list of currently available features.
3. Confirmation of working Airbnb synchronization and whether it uses iCal or an authorized API.
4. The technology stack.
5. Confirmation that complete source code is available.
6. Commercial licensing terms and any third-party dependencies.
7. Your asking price.
8. Estimated cost of any necessary customization.

**Please apply only if you already have relevant software, a demonstrable product, or a substantially developed platform.**

We are not currently seeking proposals to build an entirely new product from the beginning.

**Budget:** Based on software quality, and commercial rights. Only monthly payment solutions: i.e. 470€/month

Skills: Python, CSS, Node.js, PostgreSQL, Laravel, Redis, Flutter, Next.js, Nest.js, SaaS

I keep a working Excel file on my local machine and I need its full contents pushed into a cloud database (MySQL, SQL Server, or PostgreSQL) every time the file is saved. The moment the worksheet changes, the solution should detect the modification, connect securely to the chosen database, wipe or overwrite the target table if necessary, and insert the latest data in one pass—no incremental logic, just a complete refresh.

The workflow must run in the background without manual clicks: think a small watcher service, script, or lightweight desktop app that starts with the system, listens for file-change events, then fires the upload through the database’s standard driver or a REST gateway if that simplifies authentication.

I would like clear, commented source (Python, PowerShell, C#, or another language you are comfortable with), a simple configuration file for database credentials and sheet/table mapping, and step-by-step setup notes so I can redeploy it on another PC if needed.

Deliverables:
• Source code and packaged executable or script
• Config template and README covering prerequisites and installation
• A short demo (screencast or live session) proving that saving the workbook triggers a full table refresh in the cloud database

Success means I press Ctrl+S in Excel and, within a few seconds, the destination table shows the new data—every row, every time.

Skills: Python, C# Programming, Software Architecture, MySQL, PostgreSQL, Microsoft SQL Server, Database Development, Powershell

We are BlenEarth Global Pte. Ltd., a Singapore-based technology company developing BlenAI, a proprietary AI intelligence platform for our global SaaS ecosystem.

We are seeking an experienced Senior Python AI Backend Developer to build the first phase of BlenAI as an independent, secure, API-first platform.

Project Budget: USD 3,000 (Fixed Price)
Timeline: 30–45 Days
Project Type: Backend Development Only

Project Requirements

1. BlenAI Core Platform

* Python and FastAPI backend.
* Integration with OpenAI and other LLM providers.
* Modular AI engine architecture.
* PostgreSQL database.
* Secure REST APIs with authentication.
* Multi-tenant architecture.
* Configurable prompts, business rules, and knowledge bases.
* Structured JSON responses.
* API usage tracking and logging.

2. AI Conversation Intelligence

* Upload and process recorded conversations.
* Multilingual speech-to-text transcription.
* Conversation summarization.
* Customer intent identification.
* Buyer requirements and budget extraction.
* Objection and buying-signal detection.
* Lead scoring.
* Automated follow-up recommendations.
* Structured conversation analysis through APIs.

3. Knowledge and Intelligence Engine

* Configurable industry-specific knowledge.
* Business rules and prompt management.
* Knowledge retrieval capabilities.
* Support for future AI model integrations.
* Extensible architecture for additional AI intelligence modules.

4. AWS Hosting and Deployment

* Docker containerization.
* AWS deployment.
* PostgreSQL database integration.
* Amazon S3 for audio storage.
* HTTPS and secure API access.
* API documentation using Swagger/OpenAPI.
* Automated testing and deployment documentation.

Important Requirements

* No frontend or mobile application development is required.
* The platform must operate independently of our existing SaaS applications.
* External applications will access BlenAI through secure APIs.
* All custom-developed source code and intellectual property must belong to BlenEarth Global Pte. Ltd. under the agreed contract.
* Development must take place in our private GitHub repository.
* AWS infrastructure and AI provider accounts will remain under our company’s control.
* The developer must agree to confidentiality and IP assignment requirements.

Required Experience

* Strong Python and FastAPI experience.
* OpenAI API and LLM application development.
* PostgreSQL and REST API architecture.
* AWS deployment and Docker.
* AI agents, structured outputs, and prompt engineering.
* API security and multi-tenant SaaS systems.
* Experience with speech transcription and conversation intelligence is preferred.

Deliverables

1. Complete BlenAI Core backend.
2. Working AI Conversation Intelligence engine.
3. Configurable knowledge and business rules.
4. Secure REST APIs.
5. AWS deployment.
6. API documentation and automated tests.
7. Complete source code and technical handover.

Future Opportunities

This is Phase 1 of a larger AI platform. We plan to develop additional intelligence engines for sales, construction, procurement, inventory, financial forecasting, and business analytics.

We are looking for a reliable developer interested in a long-term working relationship.

To Apply

Please share:

1. Examples of similar AI backend projects.
2. Your experience integrating LLMs and speech-to-text models.
3. Your proposed technical architecture.
4. Your estimated completion timeline.
5. Confirmation that you can work on a USD 3,000 fixed-price contract.

We prefer experienced AI backend engineers who have built production systems, not developers specializing only in basic chatbots.

#Project Overview

We have an existing, functional SaaS analytics platform, currently in the MVP stage.

We want an experienced developer to integrate Snowflake into our existing architecture, replacing PostgreSQL for analytical data storage and querying.

This is **not a production migration**. We have no production clients or production data, and we want to keep the implementation simple, fast, and cost-effective.

#Current Architecture

- Frontend: React
- Backend: Existing APIs and services (Prisma ORM)
- Database: PostgreSQL
- Data Integration: Airbyte
- Infrastructure: AWS
- Analytics: Custom dashboards, data marts, reporting, and AI-powered queries

#What We Need

1. Set up and configure Snowflake within our existing AWS-based architecture.
2. Configure Airbyte to load analytical data directly into Snowflake instead of PostgreSQL.
3. Move existing analytical tables, schemas, and views to Snowflake.
4. Update backend connections and queries so dashboards and analytics use Snowflake.
5. Keep PostgreSQL and Prisma for application data such as users, organizations, workspaces, and dashboard configurations.
6. Test that existing dashboards, data integrations, and analytical functionality continue working.

#Key Expectations
- Reuse the existing codebase and architecture wherever possible.
- No frontend redesign or unnecessary redevelopment.
- No production data migration or historical data preservation required.
- Keep Snowflake infrastructure costs low.
- Deliver a working, tested MVP with basic technical documentation.

#What to Include in Your Proposal
Please provide:
- Your experience with Snowflake, PostgreSQL, and Airbyte.
- Estimated development hours timeline.
- Fixed-price quote
- Any opportunities to simplify or accelerate the implementation.

*We are looking for a hands-on developer who can execute this efficiently, rather than a large-scale architecture redesign or consulting engagement.*

Full-Stack AI Engineer – Multi-AI Orchestration Platform (OpenAI + Claude) with Web Research Engine

Job description:

About the project
I’m building an AI creative workspace where people think, write, design, and build in one place. It has four modes (Spark Ideas, Design, Write, Build), saved conversation history, file/image support, and subscription plans for individuals, families, and businesses. It’s designed to be calm and accessible, especially for neurodivergent users.

The next phase is the product's core: a multi-AI system that works like an AI team rather than a single chatbot. Different AI models and research tools work together behind the scenes to solve problems, research, verify information, and produce one stronger final answer.

I’m looking for an experienced full-stack developer with strong AI/LLM experience to build this across the frontend and backend.

How the system should work
A user submits one input. The system routes it to the best AI models and tools; the models process it, share findings, review each other’s work, and the system returns one improved, verified final output.

What you’ll build

Multi-AI orchestration

An AI router/orchestrator that automatically picks the best model or research tool for each task (task routing, workflow control, prompt management, input/output handling)
Integration with the OpenAI API, Claude API, and other models (Gemini, Llama, Mistral, etc.)
AI agents that can call and communicate with each other and share information
A shared workflow where one model generates an answer, another critiques or improves it, and another verifies the result.
A collaboration layer that compares responses, merges the strongest insights, and combines them into one final answe.r
A verification stage that checks for accuracy, consistency, completeness, and valid citations before the answer is shown

AI research engine

Web crawling and scraping to collect publicly available information (news, academic papers, government data, public APIs), respecting robots.txt and site terms
Real-time web research when current information is needed
Source tracking (URLs, timestamps, credibility) so users can see where information came from
AI analysis of research data to verify facts, add context, and improve answer quality

Storage and memory

Long-term memory store for user preferences, past conversations, project context, and reusable knowledge
Research results database for collected data, sources, notes, and citations

Input and output

Processing for text, documents, images, code, and structured data

Frontend and platform

Workspace UI, chat interface with streaming responses, mode switching, and a clear view of sources/citations
Accessibility (WCAG 2.1 AA), responsive/mobile layouts
User accounts, authentication, and subscription plans (Plus, Family with up to 5 profiles, Business with team workspaces and admin controls), payments (e.g. Stripe)
Performance, security, cost control for API usage, and deployment

Tech stack
[Fill in, e.g. Next.js / React, Node.js or Python (FastAPI), PostgreSQL, vector database (pgvector/Pinecone), Redis, Stripe, AWS/Vercel. Or: “Open to your recommendation.”]

Requirements

Proven full-stack experience with live SaaS products (please share links)
Hands-on experience with OpenAI and Claude APIs, including streaming and tool/function calling
Experience building multi-agent or LLM orchestration systems (e.g. LangGraph, LangChain, CrewAI, AutoGen, or custom)
Experience with RAG, embeddings, and vector databases
Experience with web crawling/scraping (Playwright, Puppeteer, Scrapy, or similar) and responsible data collection
Strong backend skills: APIs, queues/background jobs, databases, authentication
Awareness of LLM costs, latency, and rate limits
Clear communication and regular progress updates

Nice to have

Experience with AI evaluation, fact-checking, or hallucination reduction
Experience with document/image processing (OCR, PDF parsing, vision models)
Experience building accessible products

Project details

Type: [Ongoing, starting with a paid first milestone]
Budget: [$ hourly range or fixed amount]
Timeline: [e.g. start ASAP; first milestone: router + two-model workflow in 3–4 weeks]
Hours: [e.g. 20–40 hrs/week]

To apply, please include:

Links to 2–3 projects you built, ideally AI, multi-agent, or SaaS apps
Your recommended tech stack for this system and why
How you’d design the router and the generate → critique → verify workflow
How you’d keep API costs and response times under control with multiple models
Your availability and rate
Start your proposal with the word “Shapes,” so I know you read this po.st

I'm looking for an experienced Data Platform Engineer for a short, focused project to troubleshoot and improve an existing Python and Airflow data pipeline running on AWS.

The pipeline ingests data from external APIs into PostgreSQL, but we're seeing occasional duplicate records during retries and inconsistent results from incremental loads.

Scope of Work
- Review the existing Airflow DAG and Python ingestion logic.
- Identify and fix the cause of duplicate records during retries.
- Improve incremental loading to prevent missing or repeated data.
- Add basic validation and error logging.
- Test the fixes and provide a brief summary of changes.

Required Experience
- Strong Python, SQL, and PostgreSQL skills.
- Hands-on experience with Apache Airflow.
- Experience troubleshooting production ETL/ELT pipelines.
- Familiarity with AWS and reliable data processing practices.

Project Details

This is a small, short-term engagement focused on one existing pipeline, not a full platform rebuild. The expected deliverable is a tested fix with a brief technical handoff.

Please share your experience with similar pipeline issues and your availability to start.

Job Title: Build an MVP for a B2B Wholesale & Dropshipping Marketplace

Project Overview

I am looking for an experienced full-stack developer to build a lean, mobile-friendly MVP for a B2B marketplace connecting wholesalers, manufacturers, retailers, resellers, and dropshippers.

The goal is to validate the business model with real users before investing in a larger platform. I want a functional, professional website with a clean interface, reliable backend, and easy-to-use admin dashboard.


Preferred approach: Cost-effective development using modern technologies and reusable components
Project type: MVP / first version
Platform: Responsive website (mobile + desktop)

Core Features Required

1. User Registration & Login

- Buyer and supplier registration
- Login and logout
- Basic user profile management
- Supplier profiles with contact information

2. Product Listings

- Product images and descriptions
- Product categories
- Wholesale price or price range
- Minimum order quantity (MOQ)
- Supplier information
- Search and category filters

3. Buyer Features

- Browse products and suppliers
- View product details
- Submit quotation requests (RFQ)
- Contact suppliers through WhatsApp
- View basic enquiry status

4. Supplier Features

- Add and edit products
- Upload product images
- Manage product pricing and MOQ
- View and respond to buyer enquiries
- Manage basic supplier profile details

5. Admin Dashboard

- Manage buyers and suppliers
- Approve or reject supplier listings
- Add, edit and remove products
- Manage categories
- View and manage quotation requests
- Basic platform management

6. Dropshipping Support — Basic Version

- Mark products as wholesale or dropshipping eligible
- Display supplier shipping and fulfilment information
- Allow buyers to enquire about dropshipping terms

Automated inventory synchronization and order fulfilment are NOT required in this first version.

Preferred Technology Stack

- Frontend: Next.js / React
- Backend and database: Supabase / PostgreSQL
- Authentication: Supabase Auth or an equivalent secure solution
- Hosting: Vercel or a suitable low-cost alternative

Developers may propose a more cost-effective stack if it meets the requirements.

Design Requirements

- Modern, clean and professional B2B marketplace UI
- Mobile-first responsive design
- Fast loading and simple navigation
- Professional product cards and supplier profiles
- No unnecessary animations or expensive design features

Deliverables

1. Fully functional, deployed website
2. Complete source code in a GitHub repository owned by me
3. Database setup and configuration documentation
4. Admin login and access
5. Basic testing and bug fixes
6. Deployment and handover instructions
7. Ownership rights for the commissioned code and designs, documented in writing

All third-party services, paid plugins and recurring costs must be disclosed before purchase.

Important Scope Limitations

This is an MVP, not a full-scale enterprise marketplace.

The initial version does not require:

- Native Android or iOS apps
- Integrated payment gateway or escrow
- Automated supplier payouts
- Advanced real-time chat
- Logistics integrations
- Automated dropshipping fulfilment
- AI features

Who Should Apply?

Please apply if you have:

- Experience building marketplaces, e-commerce websites or SaaS platforms
- Strong frontend and backend development skills
- Experience with databases, authentication and admin dashboards
- Examples of previously completed projects
- The ability to work within a limited MVP budget

Proposal Requirements

Please include:

1. Links to 2–3 relevant projects you have built.
2. Your recommended technology stack and why.
3. Your fixed-price quotation in INR or USD.
4. Estimated delivery timeline.
5. A breakdown of the features included in your quotation.
6. Any additional hosting, API or recurring costs.
7. Confirmation that I will own the source code and deployment accounts.

Please do not submit generic proposals. I prefer a developer who understands marketplace MVPs and can recommend the simplest practical solution within the budget.

I am looking for a reliable long-term development partner if the initial MVP succeeds.

Skills: Mobile App Development, App Developer

I'm looking for someone who is honest, reliable, intelligent, and genuinely eager to learn. You don't need to know everything from the beginning. What matters most to me is your character, your willingness to grow, and your ability to pick up new technologies quickly.

I'm happy to share my knowledge and provide hands-on mentorship in Python, JavaScript, TypeScript, AWS, PostgreSQL, and other technologies based on your interests and career goals.

I'm not simply looking for someone to work with. I'd love to find someone I can genuinely invest in, guide, and help develop into a highly capable software engineer.

If you're committed, learn quickly, and consistently demonstrate progress, I'll be more than happy to share what I've learned throughout my career and help you grow into someone who can eventually carry that knowledge forward and build on it.

For me, trust, mutual respect, and long-term growth matter far more than where someone starts.

Skills: C Programming, HTML

CHILDREN'S UNIVERSITY ACHIEVEMENT CORPORATION (CUAC)

HARXGN Systems Repair, Integration, Security, Launch and Performance Agreement

Revised Consolidated Agreement — October 26, 2026

Organization: Children's University Achievement Corporation (CUAC)
Platform: HARXGN / ReadBright Path
Contractor Position: Senior Full-Stack Developer
Total Fixed Price: $1,000 USD
Project Type: One-time, fixed-price engagement
Completion Target: Seven consecutive calendar days, including weekends and holidays
Post-Launch Support: Seven consecutive calendar days after CUAC's written operational acceptance
Contract Platform: Upwork

1. Project Purpose and Required Outcome

Children's University Achievement Corporation (CUAC), a U.S.-based nonprofit literacy organization, seeks an experienced, hands-on senior full-stack developer to complete the repair, security stabilization, configuration, integration, and launch preparation of its existing HARXGN online literacy platform.

The existing technology environment includes:

WordPress and Hostinger

Cloudflare, DNS, and SSL

WooCommerce and Stripe

GiveWP donations

Lovable/HARXGN and React

Supabase and PostgreSQL

Authentication, authorization, and transactional email

Protected instructional services and learner records

APIs, payment webhooks, and automated course entitlements

This is a repair, integration, completion, and operational verification engagement—not an investigation-only assignment, redesign, rebuild, or testing-only project.

Previous technical specialists have investigated substantial system problems, performed partial repairs, and prepared extensive findings, test results, and handover documentation.

The contractor must use the existing findings and records to avoid unnecessary duplication of completed investigations and repairs.

The required outcome is a secure, fully functioning, integrated, operational, and verified launch-ready literacy platform.

Reports, audits, recommendations, prepared but unconnected code, isolated demonstrations, and descriptions of unfinished repairs do not constitute completed contractual deliverables.

Required repairs must be implemented, connected, demonstrated, and verified in the approved operational environment.

CUAC is engaging the contractor for measurable operational results, not merely time spent or effort expended.

2. Mandatory Qualifications and Pre-Engagement Readiness

The named lead contractor must demonstrate substantial hands-on experience with the technologies and responsibilities required by this engagement.

Required Qualifications

The contractor must:

Demonstrate practical experience with WordPress, WooCommerce, Stripe integrations, Cloudflare, React applications, Supabase, PostgreSQL, authentication, database security, APIs, and webhooks.

Identify any required technology with which the contractor lacks direct hands-on experience.

Demonstrate the ability to repair and connect existing systems rather than defaulting to rebuilding them.

Personally perform or directly verify substantial technical repair work.

Explain the proposed approach to payment-to-learning-entitlement integration.

Demonstrate sound account security, credential handling, and access-management practices.

Confirm availability during the agreed seven-day project schedule, including weekends.

Identify all additional personnel and their responsibilities.

Disclose material dependencies, technical limitations, availability restrictions, and foreseeable delivery risks.

Confirm the ability to perform the agreed scope within the $1,000 fixed-price budget without unauthorized additional charges.

General assurances, immediate acceptance of all conditions, or unsupported claims of expertise shall not substitute for demonstrated technical understanding.

Mandatory Pre-Start Readiness

Before technical work begins, the contractor and CUAC must document:

The approved technical scope and acceptance requirements.

The essential systems requiring access.

The status of required platform invitations.

The approved team roster.

Completed NDAs.

Known configuration and integration dependencies.

The approved first-day repair sequence.

The planned seven-day execution schedule.

The required active-repair and backup coverage hours.

The agreed official start date.

The contractor must check invitation delivery, including spam and junk folders, before reporting that access is unavailable.

The contractor must not bypass a missing invitation through password recovery, personal-account login, or unauthorized security changes.

Readiness and Deadline Feasibility

The seven-day completion commitment shall begin only after mutually documented readiness and CUAC's provision of the agreed essential access and documentation.

The contractor must disclose any known reason the proposed timeline is infeasible before accepting the contract.

CUAC is not required to authorize additional funding, a reduced scope, or a deadline extension merely because the contractor subsequently discovers that the original commitment was unrealistic.

Any revised schedule must be expressly approved through Upwork.

3. Required Systems and Repairs

A. Security, Ownership, and Recovery

The contractor shall:

Verify usable backups and documented rollback procedures before material changes.

Review the September 11, 2026 WordPress security incident using existing evidence.

Correct remaining in-scope unauthorized access, vulnerable components, malicious persistence, exposed credentials, improper privileges, and access-control defects.

Verify CUAC's ownership and authorized control of WordPress, Hostinger, Cloudflare, Lovable, Supabase, Stripe-connected systems, and organizational email.

Identify the previously reported additional or external database, determine its actual role, and safely correct or isolate harmful connections when authorized.

Preserve legitimate customer, learner, organizational, donation, and financial records.

Document completed security corrections and demonstrate their effectiveness.

Preserve existing authorized website builders, administrators, emergency recovery personnel, and approved technical collaborators.

Maintain before-and-after records of approved access and security changes.

A security audit without the required corrective action does not constitute completion.

B. WordPress, WooCommerce, Stripe, GiveWP, and Email

Repair and verify:

Website availability and store functionality.

Approved reading-kit product listings.

WooCommerce checkout and payment processing.

The correct CUAC-authorized Stripe connection and payment gateway.

Webhooks and applicable subscription processing.

Orders, purchase confirmations, and receipts.

Refunds, cancellations, renewals, and failed-payment handling.

Customer-account functionality.

The unintended $0 product or unauthorized free-access problem.

GiveWP donations, receipts, confirmations, and thank-you messages.

Transactional email configuration and delivery.

Authorized redirects, checkout completion, and notifications.

Separation of donations from program purchases.

GiveWP donations must not generate HARXGN course entitlements.

No unauthorized changes may be made to pricing, payout destinations, taxes, shipping, subscription terms, or financial settings.

CUAC must determine which Stripe account is authoritative before any production switching, reconnection, or other account-level payment configuration changes.

The contractor may conduct authorized read-only investigation of existing connections but may not independently select, replace, or activate a Stripe account.

CUAC's reading kits and program enrollment are not currently open for public sales. The contractor must not activate public purchasing or represent the system as launch-ready before written authorization.

C. Lovable/HARXGN, Supabase, Identity, and Access

Repair and verify:

The live HARXGN/Lovable application.

Correct connection to the approved production database and backend.

Registration and authentication.

Age-band intake.

Guardian consent where required.

Administrator and staff permissions.

Secure user roles and access restrictions.

Prevention of unauthorized or free learning access.

Protected instructional content and lessons.

Pre-assessments, post-assessments, and learner progress.

Results, certificates, and teacher notes.

Return-to-dashboard functionality.

Applicable access expiration.

Separation of production and isolated test environments.

The duplicate in-app Stripe checkout must be safely removed or disabled only after the approved WooCommerce checkout and purchase-to-access integration have been verified as working.

No unauthorized application route may generate learning entitlements.

No production database deletion, material migration, privilege change, or modification of real learner records may occur without CUAC's separate written authorization.

D. Automated Payment-to-Learning-Access Integration

The contractor must implement, repair, and verify the complete automated process:

Approved WooCommerce Purchase → Verified Stripe/WooCommerce Payment → Customer Identity → HARXGN/Supabase Account → Correct Learning Entitlement → Protected Course Access

Authoritative data sources must be identified and documented for:

Orders and qualifying products.

Payment and subscription status.

Customer and learner identities.

Entitlements and expiration.

The integration must correctly process:

Successful payments.

Renewals where applicable.

Failed payments.

Cancellations.

Refunds.

Entitlement expiration.

Duplicate and repeated events.

Unauthorized purchases must not create learning access.

Repeated events must not create duplicate benefits, accounts, or promotional slots.

Entitlements must be created and controlled through trusted server-side processes, not browser-controlled access grants.

E. Founding 25 Promotional Offer

Implement and verify CUAC's Founding 25 requirements:

The first 25 eligible participants making a qualifying CUAC Reading Kit purchase receive 180 days of promotional program access.

The benefit begins on the qualifying purchase date.

Each participant may receive the benefit only once.

Duplicate processing must not consume additional promotional slots.

Refunded or cancelled qualifying purchases must revoke promotional access and release the slot for the next eligible participant under CUAC's approved policy.

Donations, digital assessment books, and nonqualifying purchases alone do not qualify.

No unauthorized recurring charge may be created.

Qualifying reading kits must not be incorrectly excluded.

The contractor must demonstrate these requirements through approved test cases before production acceptance.

4. Mandatory Hands-On Participation and Team Accountability

The named lead contractor must be personally and actively engaged throughout the seven-day repair period.

The contractor must directly perform or hands-on verify approved corrections, integrations, configurations, testing, restoration procedures, and production functionality.

Supervision alone, unauthorized delegation, reporting, and administrative coordination do not satisfy the hands-on requirement.

Team Identification

Before work begins, the contractor must provide:

Full name of every participating individual.

Individually controlled professional email address.

Assigned role and technical responsibilities.

Required platform access.

Working hours and backup coverage.

Signed NDA confirmation.

CUAC's written participation approval.

Additional engineers, backup developers, project managers, and subcontractors require CUAC's prior written approval before receiving protected information or system access.

A signed NDA does not itself authorize access to CUAC systems.

Shared personal credentials and use of another team member's identity are prohibited.

The lead contractor remains accountable for all approved team members and shall coordinate their work without requiring CUAC to independently manage the development team.

Daily Reporting

The contractor must provide written daily progress reports through Upwork identifying:

Repairs actually completed.

Systems and environments affected.

Tests performed and results.

Before-and-after evidence.

Remaining defects and blockers.

Next-day priorities and responsible personnel.

Proposed changes requiring approval.

A progress report without verifiable completed work does not establish milestone completion.

5. Account Ownership, Credentials, and Security Authorization

CUAC retains exclusive ownership and recovery control over organizational accounts, systems, domains, databases, financial services, credentials, and intellectual property.

All contractor access must follow least-privilege principles through approved individual accounts and delegated access procedures.

A. Passwords, Personal Credentials, and Account Recovery

Without separate, specific, prior written CUAC authorization, no contractor or team member may:

Initiate or complete password-reset procedures.

Initiate account recovery.

Request CUAC's Yahoo or other personal email credentials.

Request authentication codes, recovery codes, security answers, or multifactor authentication secrets.

Change passwords, recovery email addresses, telephone numbers, authentication methods, or ownership settings.

Bypass multifactor authentication or other security protections.

Expand their assigned privileges.

Use technical documentation to obtain unauthorized additional access.

Access systems through another person's credentials.

Initiate recovery of Hostinger, WordPress, WooCommerce, Stripe, Lovable, Supabase, Cloudflare, or organizational email accounts.

The presence of account information or recovery details within technical handover documents does not constitute permission to use them.

Owner-level recovery and authentication must remain under CUAC's direct control or occur through an expressly approved owner-controlled procedure.

B. Access Request Requirements

Every access request must identify:

The exact platform and account.

The individual requesting access.

The task requiring access.

The minimum necessary permission.

The anticipated duration.

Operational and security consequences.

The method for revoking access afterward.

CUAC may approve, deny, limit, or postpone access.

Access to one system does not authorize changes to another.

General project authorization does not constitute permission to alter account ownership, passwords, privileges, or production configurations.

C. Existing Authorized Users

All CUAC-approved administrators, website builders, emergency recovery personnel, and legitimate collaborators must remain authorized unless CUAC approves a change.

Without prior written approval, the contractor may not:

Remove, replace, or disable existing users.

Downgrade or expand existing privileges.

Cancel existing invitations.

Modify ownership or recovery information.

Disconnect approved services.

Alter security settings.

Unexpected changes must be reported immediately and relevant evidence preserved.

D. Sensitive Changes Requiring Written Approval

Separate written approval is required for:

Live financial transactions and refunds.

Stripe account switches or payout changes.

DNS, SSL, MX, or domain changes.

Modification of real learner or customer records.

Production database deletion or material migration.

Production administrator or user-role changes.

Password resets and authentication recovery.

Security configuration changes.

Pricing, tax, shipping, or subscription changes.

Public publishing and deployment.

New recurring costs or paid tools.

Destructive or materially risky production operations.

Approval must identify the specific action and cannot be inferred from general access.

E. Incident Reporting

Suspected unauthorized access, credential exposure, unexpected permission changes, security incidents, or unintended production modifications must be reported immediately.

The contractor must stop affected activity, preserve evidence, and seek CUAC's instructions before further changes, except narrowly defined emergency action previously authorized under an agreed incident-response procedure.

Knowingly concealing a material incident or providing materially inaccurate reports constitutes a material breach.

6. Protection During Active Repairs

The contractor must remain directly available during agreed repair, deployment, and launch windows.

Before each material production intervention, the contractor must document:

The exact approved change.

Verified backups.

Rollback procedures.

The agreed work window.

Success and failure tests.

The responsible engineer and backup.

The restoration procedure.

No critical production change may proceed without the required safeguards and written authorization.

Coverage schedules must be documented in U.S. Central Time.

Any agreed continuous coverage must be provided by named, approved personnel.

Emergency Restoration

For a critical in-scope internal failure during agreed coverage, the contractor must immediately begin corrective work upon written notification.

Where an approved, tested rollback or restoration path is available, the contractor commits to restoring the affected function or its verified prior operational state within 60 consecutive minutes after CUAC's written notice.

The contractor must identify before the work window any critical system for which such restoration cannot reasonably be guaranteed.

A critical failure caused by the contractor's unauthorized actions does not excuse the contractor from immediate remediation responsibilities.

The contractor shall document the incident, response, restoration outcome, and supporting test evidence.

A temporary rollback may satisfy the immediate restoration requirement, but permanent in-scope corrections remain part of the fixed-price engagement.

A genuinely independent external-provider outage is subject to the evidence-based exception in Section 11.

Explanations, acknowledgments, and promises to repair later do not constitute completed restoration.

7. Seven-Calendar-Day Completion Deadline and First-Day Checkpoint

The completion period is seven consecutive calendar days, including Saturdays, Sundays, and holidays.

The clock begins on the mutually recorded written start date after the first milestone is funded and CUAC has provided the agreed essential access and documentation.

The contractor must identify known essential dependencies before accepting the contract.

Missing prerequisites do not automatically extend the deadline.

Any extension must identify:

The specific dependency.

Its actual effect on completion.

Work already completed.

The proposed revised deadline.

No extension, additional charge, or scope reduction is authorized without CUAC's written approval through Upwork.

Mandatory First-24-Hour Checkpoint

Within 24 hours of the approved start, the contractor shall provide:

Confirmation of accessible approved systems.

Identification of unresolved access problems.

Confirmation of team assignments.

Evidence of initial technical work or a completed repair where reasonably possible.

A schedule for the remaining project days.

Identification of material delivery risks.

Unresolved blockers must be promptly reported.

The contractor shall not initiate unauthorized account recovery, password changes, access escalation, or production changes to overcome blockers.

Failure to satisfy an applicable first-day requirement may result in immediate suspension pending correction.

Such failure does not automatically establish failure of the entire contract or override Upwork's payment procedures.

8. Fixed-Price Milestones and Acceptance Requirements

Total Fixed Contract Price: $1,000 USD

Milestone 1 — Security Repair and Stabilization

Payment: $100

Required outcome:

Remaining in-scope security, ownership, access, backup, and recovery problems corrected and retested.

Verified rollback evidence delivered.

Existing authorized user access preserved unless CUAC approved changes.

Milestone 2 — WordPress, WooCommerce, Stripe, GiveWP, and Email Repair

Payment: $100

Required outcome:

Checkout, payment processing, orders, receipts, refunds, cancellations, donations, transactional email, and unauthorized free-access problems repaired and verified.

The appropriate Stripe account must be selected and authorized by CUAC before production account changes.

Milestone 3 — Lovable, Production Database, Identity, and Access Repair

Payment: $150

Required outcome:

Working application/backend connection, database mapping, authentication, guardian consent, roles, protected learning access, and relevant checkout/access defects repaired and verified.

Production and isolated testing environments remain separated.

Milestone 4 — Automated Payment-to-Access Integration

Payment: $150

Required outcome:

Working WooCommerce/Stripe-to-HARXGN entitlement integration, payment lifecycle handling, duplicate protection, and Founding 25 functionality demonstrated and verified.

Milestone 5 — Final Integrated Launch, Handover, and Seven-Day Support

Payment: $500

Required outcome:

Remaining in-scope repairs completed; connected-system testing passed; recorded end-to-end demonstration delivered; CUAC written operational acceptance obtained; complete handover provided; and seven consecutive calendar days of agreed launch support completed.

TOTAL: $1,000 USD

No additional labor fees or recurring expenses are authorized without CUAC's written approval.

Milestone Acceptance

Every milestone submission must include:

The original problem or requirement.

The correction actually implemented.

The environment affected.

Before-and-after behavior.

Tests performed.

Results and supporting evidence.

CUAC-approved exceptions, if any.

Reports, blocked tests, recommendations, isolated demonstrations, or unconnected code do not satisfy completed-repair acceptance.

Verification must include the connected production system as safely authorized.

Synthetic accounts and Stripe test-mode verification must precede payment-affecting live tests.

Live transactions require separate written CUAC approval.

CUAC must have the opportunity to inspect and verify each milestone before approving payment, subject to Upwork's applicable review rules.

Failed in-scope acceptance tests must be corrected and retested within the agreed fixed price.

Final Milestone and Support Sequencing

The $500 final milestone is the single final performance allocation, not an additional charge or separate holdback.

Operational launch acceptance and completion of post-launch support are distinct events:

Operational Launch Acceptance: CUAC confirms in writing that the complete integrated platform passed the required acceptance testing and authorizes the start of the seven-day support period.

Final Contractual Acceptance: CUAC confirms that the required seven-day support period has been completed, the final handover is satisfactory, and all final milestone conditions have been met.

The contractor shall not represent future support as already performed.

The final milestone shall be submitted for approval only when its required deliverables, including agreed support, have actually been completed.

The parties shall arrange final-milestone funding and submission in accordance with Upwork's current escrow and milestone requirements.

If Upwork's milestone structure prevents this exact arrangement, the parties must agree in writing to an Upwork-compliant schedule before funding, without increasing the $1,000 total contract price.

No contract provision overrides Upwork's mandatory payment, review, escrow, or dispute procedures.

9. Final Operational Acceptance

Final operational acceptance requires a recorded demonstration of the functioning connected system, including:

Approved WooCommerce checkout, payment processing, and receipts.

Payment-to-learner identity and entitlement automation.

Protected course access.

Renewal, failure, cancellation, refund, expiration, and duplicate-event processing.

Correct Founding 25 qualification, promotional limits, duration, and refund handling.

Registration, age-band intake, guardian consent, and authentication.

Assessments, lessons, progress, results, certificates, and dashboard functionality.

Secure administrator access and prevention of unauthorized learning access.

Transactional emails and separate donations.

Verified backups, restoration methods, production connections, and CUAC-controlled ownership.

The contractor must provide actual test evidence and a recorded walkthrough.

An unresolved known in-scope defect prevents operational acceptance unless CUAC approves a specific written exception.

The seven-day post-launch support period begins only after CUAC's written operational acceptance.

10. Seven-Day Launch Support and Critical Restoration

The contractor shall provide seven consecutive calendar days of operational launch support after written operational acceptance, including weekends and holidays, without additional labor charges.

The contractor must remain personally available during agreed coverage hours, with named approved backup coverage where required.

Support includes the diagnosis, correction, rollback, and verification of critical in-scope failures involving:

Website availability.

Checkout and payment processing.

Registration and authentication.

Account provisioning.

Learning entitlements and access.

Webhook processing.

Application/database connections.

Security roles and permissions.

Assessments, results, progress, and certificates.

Other agreed launch-critical functions.

The contractor must promptly address unresolved preexisting in-scope defects, incomplete integrations, overlooked repairs, and regressions.

For covered critical failures with a verified available restoration path, the 60-minute restoration commitment described in Section 6 applies.

The commitment is to actual restoration or verified rollback, not merely acknowledging the incident.

A temporary rollback may satisfy immediate restoration if it returns the function to its verified operating state.

Permanent in-scope correction remains required without unauthorized additional charges.

Any promised 24/7 support must provide continuous coverage by named, CUAC-approved personnel.

Partial daily coverage is not 24/7 support.

The parties must define the actual coverage schedule and escalation contacts in U.S. Central Time before launch.

11. Contractual Performance-Refund Requirement

As a material condition of contract award, the contractor must expressly accept the agreement's 100% contractual performance-refund commitment covering funds actually paid under the contract when an expressly defined performance failure occurs.

A. Delivery Failure

The agreed in-scope platform is not fully operational and does not pass the required integrated acceptance tests by the agreed seven-calendar-day deadline, unless CUAC expressly approves a written extension or a documented contractual exception applies.

B. Critical Restoration Failure

During contracted active-repair or post-launch support coverage, the contractor fails to fulfill an applicable 60-minute restoration or verified rollback obligation for an in-scope critical internal failure, except to the extent a documented contractual exception applies.

The performance obligation includes incomplete in-scope repairs, overlooked defects, integration failures, security defects, application/database failures, and regressions.

A contractor may not automatically disclaim an agreed in-scope defect solely because it existed before the engagement.

Upon an expressly defined performance failure, CUAC may terminate the engagement and request the contractual performance refund.

The contractor shall cooperate with applicable Upwork refund procedures and initiate refunds within the contractor's control within 24 hours of a valid written demand.

This is a contractual commitment between the parties, not a guarantee that Upwork will automatically refund released money or enforce the provision.

Upwork's applicable payment, escrow, review, and dispute rules remain controlling.

A genuinely independent external-provider outage may qualify for a limited exception only when supported by contemporaneous objective evidence and only for the period directly affected.

Ordinary misconfiguration, improperly managed secrets, webhook failures, and other agreed in-scope defects do not automatically qualify.

CUAC retains the right to provide truthful feedback consistent with Upwork's policies. No refund may be conditioned on withholding such feedback.

12. Confidentiality, Handover Documents, and Sensitive Information

All CUAC records, findings, architecture information, credentials-related documentation, database information, and handover materials are confidential.

They may be used only for expressly authorized project purposes.

Protected information includes:

Previous investigation reports.

Repair records and technical handovers.

Architecture and database mappings.

Account inventories.

Configuration details.

Security findings and incident reports.

Learner, customer, donation, and payment records.

Access and recovery-related technical information.

The contractor may not use information from the reports to initiate unauthorized account recovery, bypass security, expand permissions, or alter account ownership.

Confidential materials may not be redistributed to unidentified personnel or third parties without CUAC's written authorization.

Only approved individuals covered by executed NDAs may receive protected information.

Copies and Preservation

The contractor must maintain a record of personnel who receive or download confidential project materials.

Upon termination or written request, the contractor shall return or securely delete copies as directed, except records required for applicable legal, Upwork, or dispute-preservation obligations.

The contractor must confirm the disposition of copies retained by approved team members.

No records relevant to a pending payment dispute, security incident, or legal preservation duty shall be destroyed.

Actual passwords, recovery codes, API secrets, and security tokens must not be reproduced in ordinary handover reports.

Potentially exposed active credentials must be reported immediately for owner-controlled remediation.

13. Suspension, Termination, and Withdrawal

Either party may ordinarily terminate the engagement through Upwork upon two calendar days' written notice, subject to applicable platform procedures.

Termination does not eliminate accrued obligations, security responsibilities, handover duties, or applicable payment and dispute rights.

Immediate Security Suspension

CUAC may immediately suspend work and revoke access upon a reasonable identification of:

Unauthorized password-reset or recovery attempts.

Requests for personal owner credentials or authentication codes outside an approved process.

Unauthorized access escalation.

Unauthorized modification or removal of existing user permissions.

Access by unidentified or unapproved personnel.

Unauthorized financial, production, or database changes.

Material misrepresentation of access methods, completed work, or test results.

Concealment of a material security incident.

A credible threat to CUAC's ownership or system security.

Upon written suspension notice, the contractor and team must cease system access, testing, credential recovery, and technical modifications unless CUAC expressly authorizes a limited action for evidence preservation or emergency protection.

Immediate Termination

CUAC may immediately terminate for material breach, serious unauthorized security activity, or other grounds permitting immediate termination under the agreement and applicable Upwork procedures.

Ordinary termination without established material breach remains subject to the applicable notice and platform rules.

A contractor may not use voluntary withdrawal to avoid accrued contractual obligations.

Termination Cooperation

Upon termination, the contractor must:

Cease unauthorized technical activities.

Identify all systems accessed and accounts used.

Provide records of completed work and modifications.

Disclose pending changes, access requests, and incidents.

Preserve relevant technical and project evidence.

Cooperate with access revocation.

Return or properly dispose of protected materials under Section 12.

Provide handover information for work actually performed.

CUAC retains authority to revoke invitations and delegated permissions independently.

Disputes and refunds shall be handled through applicable Upwork procedures and other available lawful remedies.

14. Final Handover Requirements

The contractor must provide a complete CUAC-controlled handover package containing:

Current system architecture.

Production and external database mapping.

Authoritative payment, order, identity, subscription, and entitlement sources.

Complete repair register and verification matrix.

Before-and-after testing evidence.

Recorded end-to-end walkthrough.

Backup, restoration, and rollback instructions.

Administrator and staff access inventory.

Confirmation of CUAC ownership and recovery control.

Record of approved secret or credential rotations without exposing actual secrets.

Documentation of recurring costs.

CUAC-approved exceptions.

Configuration and deployment instructions.

Full list of personnel who accessed CUAC systems.

Record of account-permission changes.

Status of all temporary access and invitations.

Confirmation that no undisclosed contractor-controlled dependency remains.

List of unresolved defects or security issues.

All paid work and applicable configuration information must remain available through CUAC-controlled accounts, subject to applicable third-party licenses.

Temporary access must be safely revoked or transferred at the end of the engagement.

No undisclosed contractor-controlled account or workspace may remain essential to CUAC's normal operations.

15. Required Contractor Acceptance Before Award

Before contract funding, the selected contractor must expressly accept this entire agreement through Upwork.

Mandatory Written Acceptance

"I have reviewed and accept CUAC's complete $1,000 fixed-price HARXGN systems repair, integration, security, launch, and performance agreement.

I acknowledge and accept the five milestones; the seven-consecutive-calendar-day completion target and agreed readiness conditions; weekend availability; personal hands-on technical participation; first-24-hour checkpoint; daily evidence-based progress reports; written authorization requirements; seven-day post-operational-acceptance support; and the defined 60-minute critical restoration obligation.

I accept the contractual performance-refund provisions, subject to the express exceptions and applicable Upwork procedures.

I understand that CUAC retains exclusive ownership and recovery control of its systems and accounts.

I will not request or use personal owner credentials, initiate account recovery, modify authentication settings, remove authorized users, expand permissions, or perform sensitive production changes without specific written authorization.

I will identify every participating team member, their individual email address, technical responsibilities, NDA status, access requirements, and coverage hours before work begins.

I acknowledge that reports, isolated tests, recommendations, and unconnected code do not satisfy operational milestone requirements.

I have disclosed my actual technical experience, material limitations, essential dependencies, and scheduling risks.

I will not request unauthorized additional charges, substitute personnel without approval, represent incomplete work as completed, or rely upon conflicting earlier proposal terms.

I accept the agreed confidentiality, security, verification, support, handover, suspension, termination, and Upwork dispute requirements."

Required Information Before Contract Funding

Named Lead Engineer: __________________________

Approved Additional Engineers: __________________________

Approved Backup Personnel: __________________________

Approved Project Manager (if any): __________________________

Individual Team Member Email Addresses: __________________________

Defined Responsibilities: __________________________

Coverage Hours (U.S. Central Time): __________________________

Written Project Start Date: __________________________

Seven-Day Completion Deadline: __________________________

Essential Access and Dependencies: __________________________

Pre-Start Readiness Confirmation: __________________________

NDA Completion: __________________________

CUAC Team Approval: __________________________

Contractor's Written Upwork Acceptance: __________________________

END OF CONSOLIDATED AGREEMENT

Total Contract Value: $1,000 USD
Completion Target: Seven Consecutive Calendar Days
Post-Launch Support: Seven Consecutive Calendar Days
Required Outcome: Fully Repaired, Integrated, Secure, Demonstrated, and Operational HARXGN Literacy Platform

Hi Upwork,

I am seeking skilled web developers in HTML, Javascript, CSS, API and Database Layer who can support developing a platform similar to that of Jobber, temper.works and task rabbit. I am hoping it would be collaborative and creatively developed and we can start off with realistic expectations.

Please reach out and we can have a consultation together.

Kind regards,
Bolu Salami

Hi there,

I am launching a luxury fashion e-commerce store built on Shopify and powered by BrandsGateway as my primary supplier.

I am looking for a dedicated Hands-on 360° E-Commerce Operator who will actively manage, execute, and operate the store’s technical setup, inventory, and daily operations long-term.

CRITICAL REQUIREMENT: Please do not apply unless you have direct, hands-on operational experience integrating BrandsGateway into Shopify and managing ongoing store workflows.

Target Market & Logistics Setup:

Primary Focus Market: Saudi Arabia (KSA)

Secondary & Regional Markets: GCC & Worldwide (Open Global Scope)

Primary Warehouse Location: Shipped directly from BrandsGateway warehouses in Italy

Operational Currencies: SAR, USD, EUR

Key Scope & Daily Responsibilities (Store Operations):

Shopify Store Setup & Operations: Designing, configuring, and operating a premium Shopify store optimized for luxury fashion branding.

BrandsGateway System Integration: Full technical management of live inventory, automatic catalog updates, and price synchronization via BrandsGateway app/API.

Pricing & Financial Configurations: Setting up and managing automated pricing rules (handling currency conversion, DDP/DDU shipping rates from Italy to Saudi Arabia/GCC/Worldwide, customs, profit margins, and payment gateways).

Fulfillment & Policy Management: Daily order routing, tracking integration, customer service workflow setup, and managing returns strictly aligned with supplier policies.

Operational Troubleshooting: Continuous monitoring to resolve sync glitches, out-of-stock discrepancies, or checkout issues in real-time.

How to Apply / Proposal Requirement:
*** Please start your application with the phrase: "LUXURY OPERATOR" ***

In your application, please state clearly:

How many Shopify stores powered by BrandsGateway have you operated or built?

Can you share links or screen-share examples of previous BrandsGateway/Shopify operations you managed?

How do you handle BrandsGateway inventory sync intervals and safety buffer stock to avoid selling out-of-stock luxury items?

What is your strategy for setting up DDP (Delivered Duty Paid) shipping rules and customs handling specifically for orders shipped from Italy to Saudi Arabia and the GCC?

Best regards,
Majed

I'm looking for a reliable full-stack developer to automate the weekly sales reporting process for an existing project built with Laravel on the backend and Next.js on the frontend.

The goal is to streamline the reporting workflow by developing the necessary APIs and integrating an automation workflow that generates and sends weekly sales report notifications with minimal manual intervention.

I'm looking for someone who can understand the existing codebase, suggest practical solutions, and deliver clean, maintainable work.

Responsibilities

Review the existing Laravel backend and Next.js frontend to understand the current sales data and reporting workflow.
Develop or update Laravel APIs required to retrieve and process sales data for automated reporting.
Set up the weekly sales report automation workflow using n8n.
Configure scheduled report generation and notifications so reports are delivered reliably each week.
Work with the existing MySQL and/or PostgreSQL database structure as required.
Test the complete workflow, handle potential errors, and ensure the automation runs consistently.
Communicate progress clearly and document any important setup or configuration details.

Required Skills and Experience

Strong experience with PHP and Laravel.
Solid knowledge of Next.js and JavaScript/TypeScript.
Experience designing and integrating REST APIs.
Good working knowledge of MySQL and PostgreSQL.
Hands-on experience with n8n or similar workflow automation tools.
Experience working with existing applications and extending their functionality without disrupting current features.
Good English communication skills and the ability to provide regular updates.

What I'm Looking For

I'm looking for someone who is dependable, communicates clearly, and pays attention to detail. You should be comfortable working independently, asking questions when requirements need clarification, and suggesting better approaches when appropriate.

Please focus on delivering a reliable, well-tested solution rather than a quick workaround.

To Apply

Please briefly share:

Your relevant experience with Laravel, Next.js, and n8n.
One or two examples of similar API development or workflow automation projects you've worked on.
Your proposed approach to automating a weekly sales report.
Your estimated timeline for completing the work.

Potential for Future Work

This project may lead to ongoing collaboration for future improvements, new features, and additional development work if we're a good fit.

I'm looking forward to working with someone who can help make this reporting process reliable and easy to maintain.

I have an existing web app built with Next.js and Supabase, hosted on Vercel. It is already in daily use. I'm looking for an experienced developer to review it and help turn it into a commercial SaaS product.

Stage 1 (this job):
- Review the existing code and point out issues with security, structure and performance
- Recommend how to make it production-ready and usable by multiple businesses
- Give a quote and timeline for the next stages

You'll need:
- Strong Next.js, React and Supabase/PostgreSQL experience
- Experience building and launching SaaS products
- Experience integrating third-party APIs
- Clear communication and some overlap with Australian business hours (AEST)

To apply:
- Links to 2–3 live apps you've built (Next.js/Supabase preferred)
- A short description of the most similar project you've worked on
- Start your proposal with the word "Ledgerline" so I know you've read this

An NDA must be signed before any project details or code are shared.

The budget is for Stage 1 only. Further stages will be quoted separately.

Build a B2B SaaS Dashboard for One-Click Employee Offboarding across 5 Core Apps (MVP)

Project Description / Scope of Work:

Overview:
We are looking for an experienced Full-Stack Developer (or small team) to build a Minimal Viable Product (MVP) for "OffboardPulse"—a lightweight B2B web application that helps small-to-medium businesses (10–50 employees) revoke former employee access across multiple SaaS applications in 1 click.

When an employee leaves a company, business admins waste hours logging into 5–10 different websites to revoke access. This tool connects via APIs to automate user deactivation, prevent data security risks, and eliminate wasted software license seats.

Key Features & Requirements:

1. Client Admin Dashboard
- Employee Directory: Simple UI to add employees, view their current status, and manage their assigned software seats.
- App Connection Hub: Secure OAuth 2.0 & Admin API Key connection manager where admins connect their company’s workspace accounts.
- One-Click Offboard Action: Triggering "Offboard Employee" sends concurrent API requests to revoke user access across all linked apps.
- Audit Log & Timestamp History: Visual activity log documenting successful revocations for company compliance records.

2. Core App Integrations (5 Initial Apps for MVP)
Automated API calls must handle the following deactivations:
- Google Workspace Admin SDK API: Set user account status to "suspended".
- Slack Admin / SCIM API: Set member profile status to "deactivated".
- GitHub REST API: Remove user from organization membership and revoke repository access.
- Figma Admin API: Revoke active design seat / remove member from team space.
- Notion Admin API: Remove user from workspace team members list.
- Fallback Checklist: For non-connected apps, display a clean checklist with direct deep-links to the app’s admin settings page.

3. Authentication & Billing Integration
- Secure Admin Authentication (Email/Password + Google OAuth login).
- Stripe Checkout or Lemon Squeezy integration for monthly recurring subscription tiers ($29/mo and $49/mo).

Preferred Tech Stack:
- Frontend: Next.js (React) + Tailwind CSS (clean, modern responsive design)
- Backend: Node.js / Serverless API routes
- Database & Auth: Supabase (PostgreSQL) or Firebase
- Deployment: Vercel / Cloudflare

Freelancer Qualifications:
- Demonstrable experience building production-ready Next.js / React SaaS MVPs.
- Direct expertise working with 3rd-party REST APIs, OAuth 2.0 flows, and webhooks.
- Ability to write clean, maintainable code using standard developer API libraries.

Milestones & Deliverables:
- Milestone 1 ($25%): Database Schema, Responsive UI Mockup, User Auth & App Dashboard setup.
- Milestone 2 ($35%): OAuth Connection Engine + API Integrations for Google Workspace, Slack, and GitHub.
- Milestone 3 ($25%): API Integrations for Figma & Notion + 1-Click Offboarding Engine & Audit Log UI.
- Milestone 4 ($15%): Stripe/Lemon Squeezy Billing Integration, Bug Testing & Live Production Deployment.

How to Apply:
Please start your bid with the phrase "Offboard SaaS Developer" so I know you read the complete scope.
Please include:
1. Links to 2–3 live web applications or SaaS tools you have built.
2. Estimated timeline to deliver this MVP (Target: 3 to 5 weeks).
3. The tech stack you recommend for fast, scalable execution.

Skills: PHP, Software Architecture, MySQL, Node.js, AngularJS, OAuth, Full Stack Development, API Development, Next.js, SaaS Development

Job Description
I need an experienced full-stack developer to design and build a web application that integrates with M-Pesa for payments, using React on the front end, Node.js on the back end, and PostgreSQL as the database.
Project overview
The system should let users initiate and complete M-Pesa payments (STK Push / C2B), record transaction status in real time via callbacks, and manage related data (users, transactions, and core records) through a clean React interface and a well-structured Node.js API. Exact feature scope will be refined in the first week once we align on priorities. The foundation needs to be solid, secure, and maintainable.
Technical requirements
• React (modern functional components and hooks)
• Node.js with a structured API (Express or equivalent)
• PostgreSQL (schema design, migrations, and queries)
• M-Pesa Daraja API integration (authentication, STK Push, callbacks, and transaction status handling)
• Proper error handling, logging, and basic security practices
• Environment-based configuration (dev / staging / production)
What I’m looking for
• Proven experience with the stack above, especially real M-Pesa integrations
• Ability to work independently on an hourly basis with clear weekly progress updates
• Willingness to discuss architecture choices and document key decisions
• Clean, readable code and a practical approach to deployment
Timeline and availability
Estimated 3–6 months on an hourly basis. Medium skill level is appropriate; reliability and clear communication matter more than the lowest rate.
This is a multi-month engagement. Please review your calendar carefully and disclose in your proposal any holidays or planned periods of limited availability in the next 3–6 months. Short, advance-communicated breaks are acceptable; I will hold you to the availability you state.
Please also include:
• 1–2 examples of previous M-Pesa or similar payment-gateway work
• A short note on how you would structure the initial API and database schema
• Your typical weekly availability
I’m ready to start soon and will provide more detailed requirements once we connect.

Looking for a Data Engineer/Analyst who has experience with Databricks.
Experience with PostgreSQL and AWS cloud is an added advantage.

No agencies...

We are a small startup building a subscription-based web application that helps small businesses manage clients, invoices and recurring payments in one dashboard. We have a finished product spec and wireframes, and we need an experienced full stack developer to turn them into a production-ready MVP.

We have a web application and want to add AI-powered features using the OpenAI API. We’re looking for an experienced full stack developer who can work inside our existing codebase, solve problems independently, and keep us updated without being chased.

What you’ll work on

Build and improve features in React and Next.js with TypeScript
Develop Node.js / Express services with clean REST API endpoints, documented with OpenAPI
Integrate the OpenAI API into our existing app (AI features, prompt handling, error handling, cost control)
Manage and optimize our PostgreSQL database (Supabase experience is a plus)
Integrate third-party APIs
Implement authentication and role-based access
Fix bugs and leave clear notes so the next developer isn’t guessing

Required

React.js / Next.js
Node.js / TypeScript / JavaScript
PostgreSQL
REST API design and integration
OpenAI API / AI integration
Git / GitHub

Nice to have

Vercel or AWS deployment
Tailwind CSS or Material UI
Stripe payments or subscriptions
MongoDB / MERN stack experience

How we work

Fixed-price milestones, starting with one small paid milestone. If it goes well, we continue.
A plain-English plan and written scope before coding starts
Regular progress updates, and early warning if anything threatens the deadline
Readable, maintainable code with handover notes

To apply, please include:

One project where you integrated an API or AI feature into an existing app, and what the result was
Your availability and how soon you can start
Your proposed first milestone

We’re happy to hire for the long term if the first milestone goes well.

Freelance Full-Stack Developer — Telugu AI Telecalling MVP


Engagement: Fixed-price project with milestone payments
Project: Custom AI telecalling platform for an Indian startup

About the project

We are building a custom AI telecalling platform that uses existing AI voice APIs and an authorized Indian telephony provider. We are not looking to train a speech or language model from scratch.

The first version must demonstrate natural Telugu conversations suitable for customers in Andhra Pradesh and automatically qualify leads from actual phone calls.

Required deliverables

1. A basic secure client/admin login and dashboard.
2. Lead upload using CSV and campaign creation.
3. Configurable Telugu call script and qualification questions.
4. Integration with an existing AI voice API and an appropriate Indian telephony provider.
5. Real outbound test calls with transparent AI identification.
6. Automatic call outcomes, lead classification, summaries and callback status.
7. Call usage and estimated cost reporting.
8. Opt-out handling, duplicate prevention, retry limits and basic access controls.
9. Deployment, documentation, source code and handover.

Preferred skills

- Backend development using Python/FastAPI or equivalent.
- Frontend development using React/Next.js or equivalent.
- PostgreSQL or a comparable managed database.
- Experience with real-time voice APIs, audio streaming and telephony integration.
- Webhooks, authentication, logging, error handling and secure API-key management.
- Ability to demonstrate an existing voice or telephony integration.

Before applying

Please provide:

- A live demonstration of a relevant working project.
- Your proposed architecture and voice/telephony providers.
- A fixed-price quote broken into milestones.
- Expected third-party usage charges, separately from development fees.
- A realistic delivery schedule.
- Confirmation that the company will own the source code and project accounts.

Important: Payment is tied to demonstrated deliverables, including a working phone-call integration. A dashboard-only demonstration is not sufficient.

Please do not propose training a new AI model from scratch or require an expensive annual vendor commitment.

Skills: PHP, JavaScript, Python, Website Design, Mobile App Development, Android, Full Stack Development, Backend Development, AI Chatbot Development, AI Voice Agents