Freelance HTML developer jobs

we lost a website due to server failure. we have recovered it from internet archive. we need a developer to rebuid it fast and republish it. 2 languages few pages.

I’m looking for an experienced web developer to help assess the feasibility of creating a UK-based adult lifestyle membership website exclusively for people aged 50 and over.

I already have a working HTML design prototype showing the general appearance and layout I would like.

The eventual website would include:

- Member registration and profiles for individuals and couples
- Private messaging between members
- Photo uploads and privacy controls
- Location and postcode-based member searching
- Online status indicators
- Administrator tools for profile verification and moderation
- Mobile-friendly design
- Appropriate security, UK data protection and online safety measures, including age assurance

**IMPORTANT: This initial job is NOT to build the complete website.**

I am looking for a small, fixed-price technical feasibility assessment with the following deliverables:

1. Recommend suitable, actively maintained dating or community software that could be adapted for this project, rather than developing everything from scratch.
2. Explain the software’s licensing costs, ongoing costs, limitations and suitability for an adult-oriented membership website.
3. Provide a small demonstration or walkthrough showing how the proposed software works and how my existing HTML design might be incorporated.
4. Identify significant technical, privacy, security and UK regulatory considerations that would need specialist review before launch.
5. Provide a separate, itemised quotation and estimated timescale for developing the full website.

My initial budget is approximately $300 USD for this assessment only. I understand that full development would be a separate project with a substantially larger budget.

I am not a technical expert, so I would appreciate clear explanations in plain English.

Please include examples of relevant membership, dating or community websites you have worked on, and confirm that you are comfortable working on a lawful adults-only lifestyle website.

I am exploring options and am not yet committing to full development.

I need help creating a website for my business. The project involves building a functional online presence that is clean, user-friendly, and easy to navigate. I am looking for someone who can handle the development process from start to finish and deliver a reliable website that meets my needs. Please share relevant examples of similar work and your approach to building and launching a website.

I need help building a custom element in GoHighLevel that I have already created in WordPress. The goal is to recreate the same functionality and user experience in GoHighLevel so it works smoothly within the platform. I’m looking for someone who can translate the existing WordPress setup into a custom GoHighLevel element and ensure it performs reliably. Please share relevant experience with custom element development and similar platform integrations.

Squarespace & Launch VA — AI-Assisted Website Updates, Courses & Customer Support

I’m Katie, founder of Encoded Frequencies, an online sound healing and energy education business offering memberships, courses, and live events.

I’m looking for an experienced, proactive VA for an ongoing role, starting at approximately 20 hours per week. Ideally, you’re based in the Philippines with some availability during Brisbane working hours.

What you’ll own

I provide the event idea, wording, dates, pricing, and content. You turn that brief into a complete, tested setup and manage the follow-through.

Your responsibilities include:

* Building and updating Squarespace landing pages, courses, and membership content.
* Uploading recordings, audio files, and course materials.
* Creating Zoom events and adding them to the calendar.
* Formatting and scheduling announcement emails, reminders, and follow-ups using my wording.
* Updating website banners and event information.
* Checking registration, checkout, links, and member access before launch.
* Answering routine customer emails and resolving access questions.
* Helping manage our Circle community.
* Maintaining ClickUp tasks, deadlines, and launch checklists.
* Coordinating with our audio and social content team.

Squarespace code and AI skills

You must be comfortable using ChatGPT or similar AI tools to help create, edit, and troubleshoot HTML/CSS for Squarespace code blocks.

This includes:

* Improving existing custom sections so they look polished on mobile and desktop.
* Fixing spacing, alignment, image sizing, text wrapping, and button layouts.
* Understanding and checking AI-generated code sufficiently to troubleshoot problems.
* Testing changes on mobile and desktop, including checking for horizontal scrolling and broken layouts.
* Keeping styling scoped to the intended section or page.
* Preserving the existing design and getting my approval before changing page layouts.

Please include an example of a Squarespace section you’ve coded or improved, ideally showing both mobile and desktop views. Explain your contribution and how you used AI, if applicable.

Who you are

You have practical experience with Squarespace courses, memberships, and online launches. You’re organised, reliable, warm with customers, and able to work independently.

You notice missing details, ask clear questions, and take responsibility for finishing and checking your work.

Experience with MailerLite, Zoom, ClickUp, Circle, and Canva is helpful. Familiarity with sound healing or personal development is welcome; relevant skills and reliability matter most.

I provide the main promotional wording and creative direction. Audio editing and video production are handled separately.

Working arrangement

Approximately 20 hours per week initially, with agreed working hours, deadlines, and turnaround times. Hours may increase as the role develops.

This is an ongoing opportunity beginning with a paid trial project. I’m looking for someone who can reserve consistent time for the business and provide dependable support around launches.

To apply, please include:

1. Your experience with Squarespace courses and memberships.
2. An online event or course launch you helped set up, explaining your responsibilities.
3. An example of your Squarespace custom code work on mobile and desktop.
4. How you use ChatGPT or other AI tools and check the results.
5. Your experience with the other tools listed above.
6. Your hourly rate in USD, weekly availability, and working hours in Brisbane time.

Please begin your application with “Encoded Frequencies” so I know you’ve read the full description.

I need one eBay listing written for a natural Himalayan salt lamp. This is a small, clearly scoped task, and I’ll pay the moment it’s delivered.

What I need:

A title that uses all 80 characters and is built on real eBay search terms
A complete set of item specifics (brand, material, color, size, weight, type, and so on)
A clean, mobile-friendly description with no HTML templates and no external links
5 keyword suggestions you’d target, each with a one-line reason

What I’ll provide:
Product photos, size and weight, and the price range.

Deadline: 12 to 24 hours

To apply: start your proposal with the title you’d write for this listing. Proposals without a sample title won’t be reviewed.

We have a near-complete WordPress website for a Singapore property agent (new condo launches). The core build is done by our existing developer: custom block theme, custom post types for projects, districts, MRT stations, schools and articles, plus a project data import. What remains is visual polish to match our Figma design exactly, followed by ongoing maintenance. We want to go live as soon as possible.

Working with our existing developer: You will work alongside our existing developer, who continues to own the custom code (project data import and sync, search and filters, Google Maps integration). You will own the visual layer and content. We will set up a 30-minute handover call where he walks you through the custom blocks and how project data works, and we will keep a shared change log so your work and his never overlap or overwrite each other.

Part A: One-time visual fixes (fixed price)
- Compare each page on our staging site against the Figma design and fix all visual differences: spacing and padding between sections, text alignment, font sizes and weights, image cropping and ratios, overlapping text, and missing icons.
- About 14 page templates: Home, Project page, New Launch hub, District hub and profile, MRT line and station pages, Primary School hub and profile, TOP Year page, Tenure hub plus 3 tenure pages, Insights (blog) listing and article pages, Resale page, Showflat page.
- Fix broken internal links and buttons (e.g. links still pointing to old /wordpress/ paths, "Browse all" and "Explore all" buttons not linking to the right pages).
- Check and fix every page on mobile and tablet.
- Use the existing custom blocks and theme styles wherever possible so the site stays editable from the WordPress admin. No new page builders or heavy plugins without asking first.
- We will give you a numbered list of known issues, but we expect you to find and fix any other differences from the Figma too.

Part B: Ongoing maintenance (adhoc or ongoing to be discussed, estd 2-6hrs/month)
- Edit text, images, FAQs and page sections.
- Add or update project listings: rename projects when they get an official name, upload new project images and details, and update project content from an Excel sheet we provide.
- Publish new blog articles we write (formatting, images, categories, internal links).
- Monthly WordPress core, theme and plugin updates, with a backup before every update, coordinated with our existing developer so updates do not break his custom code.
- periodic data upload/refresh
- fix any aesthetic-related issue when raised

Not in scope: changes to the project data import and sync code, search and filter logic, or the Google Maps integration. These stay with our existing developer. If you spot a bug in these areas, log it in the shared change log and flag it to us rather than changing the code yourself.

How we work:
- All changes are made on the staging site first, never directly on the live site.
- Take a full backup before starting and before any major change.
- Log every change you make (date, page, what changed) in our shared change log.

Must have:
- Solid WordPress experience, including block themes (Gutenberg / Full Site Editing) and editing theme CSS and basic PHP templates.
- Able to follow a Figma design accurately, down to spacing and typography.
- Comfortable working in a codebase someone else built, and communicating clearly with another developer.
- Good written English and responsive within 24 hours on weekdays.

Nice to have: Experience with custom post types and ACF, real estate or listing websites.

Webopedia is a long-running tech and crypto reference site. We're expanding our crypto exchange coverage into the German market and need a native German editor who knows the crypto space well and can proofread translated copy and ensure that it reads as if it were written for German readers from the start.

The project
You'll proofread and edit around 20 pages from English into German (de-DE). The pages fall into three types:

- "Best" comparison pages, such as the best crypto exchanges for a given use case
- Exchange reviews covering fees, features, security, supported assets, and usability
- Educational guides and explainers, such as how exchanges work and how to buy crypto safely

You'll receive machine-assisted German drafts and turn them into polished, natural German that's accurate and ready to publish. This means more than translation. We want terminology that German crypto users actually use, examples and references adapted for the local market where needed, and close attention to anything that could mislead readers about risk or regulation.

What we're looking for
- Native-level German, with a strong command of English
- Proven experience writing or editing crypto content, ideally about exchanges, trading or DeFi
- Familiarity with how German readers search for and talk about crypto, including which terms stay in English and which get localised
- Awareness of the regulatory context for crypto in Germany and the EU (BaFin, MiCA) and of the need for balanced, non-promotional risk language
- Attention to detail with numbers, fees and product names, plus the judgement to flag anything in the source that looks wrong or outdated
- SEO awareness is a strong plus, especially for headings, meta titles and descriptions in German

Working details:
- Volume: about 20 pages of varying length (roughly 2,000-3,000 words each)
- Timeline: 26 October, with completion targeted by 10 November
- Workflow: HTML, Google Docs or WordPress drafts, with comments for queries
- Budget depends on experience
- There's potential for ongoing work on further German content if the project goes well

To apply, please include:
1. Two or three links to German crypto content you've written or edited
2. A short note on how you handle terms that German crypto users tend to leave in English (e.g. "Staking", "Wallet", "Spot Trading")
3. Your rate and availability over the next 4 weeks

Applications without German crypto writing samples won't be considered.

We’re looking for an experienced Shopify designer/developer to create a polished, conversion-focused online store for a premium direct-to-consumer fashion brand.

The website should combine strong visual direction with an intuitive shopping experience. Thoughtful typography, beautiful product presentation and excellent mobile usability are essential, alongside practical conversion rate optimisation and a solid SEO foundation.

Scope of Work

• Design and customise a Shopify theme to reflect our brand identity.
• Create the homepage, collection and product templates, About and Contact pages.
• Set up clear navigation, collections, search and relevant product filters.
• Configure products, sizes, colours, variants and inventory.
• Configure payments, shipping and essential customer notifications.
• Ensure a consistent experience across desktop, tablet and mobile.

Conversion Rate Optimisation

• Structure pages around product discovery, buying confidence and clear calls to action.
• Improve product presentation with image galleries, size and fit guidance, fabric details and care information.
• Clearly communicate delivery, returns and exchanges.
• Incorporate genuine customer reviews and relevant trust signals where available.
• Recommend useful cross-sells, outfit combinations and bundles to support average order value.
• Optimise the cart and purchase journey within Shopify’s capabilities.
• Set up or verify GA4 ecommerce tracking and key conversion events.
• Provide a prioritised post-launch testing roadmap. We value measurable improvements rather than unsupported conversion guarantees.

SEO & Performance

• Research relevant keywords and map them to core pages and collections.
• Optimise page titles, meta descriptions, headings, URLs and internal links.
• Add descriptive image alt text and optimise image sizes.
• Review product structured data, indexing, canonical tags and the XML sitemap.
• Set up or verify Google Search Console.
• Improve loading performance and minimise unnecessary apps or scripts.
• Include URL mapping and redirects if existing URLs change.

Deliverables

• Approved design direction and a fully implemented Shopify storefront.
• Reusable sections that our team can edit.
• Tested navigation, variants, forms, cart and checkout.
• A summary of SEO, performance and tracking work completed.
• A short handover video or session.
• Clearly defined post-launch bug-fix support.

Please work in an unpublished theme until launch approval. Any paid themes, apps or ongoing subscriptions must be discussed before use.

Who We’re Looking For

• Proven Shopify design and development experience, ideally with premium fashion or apparel brands.
• Strong visual judgment and mobile UX skills.
• Confidence with Liquid, HTML, CSS and JavaScript.
• Practical experience with CRO, technical SEO and ecommerce analytics.
• Clear communication, realistic timelines and attention to detail.

To Apply, Please Include

1. Two or three relevant live Shopify stores and your specific contribution to each.
2. One CRO example with the problem, changes made and measured results, including the comparison period.
3. Your approach to creating a premium fashion shopping experience.
4. What your SEO and tracking work would include.
5. Your recommended theme approach and any anticipated app requirements.
6. Your estimated timeline and fixed-price quote, separating design/development, CRO and SEO.
7. What is included in revisions, launch support and ongoing costs.

Please begin your application with “FASHION” so we know you’ve read the brief.

We’re interested in a reliable partner who can support ongoing improvements after launch.

I’m looking for an experienced WordPress developer who can fix some issues with my website’s header and footer using Elementor.

The main goal is to make the header and footer look professional, function correctly, and display properly across desktop, tablet, and mobile devices.

Tasks & Requirements:

* Fix existing header and footer layout issues using Elementor or Elementor Pro.
* Ensure the header and footer are fully responsive across all devices.
* Fix spacing, alignment, typography, and styling issues.
* Resolve any issues with sticky headers, navigation menus, or mobile menus, if needed.
* Ensure the header and footer display correctly across all website pages.
* Maintain the existing website design and avoid unnecessary changes.
* Test everything after completing the fixes.

Required Skills:

* Strong experience with WordPress and Elementor.
* Experience with Elementor Theme Builder.
* Good knowledge of responsive design and CSS.
* Ability to troubleshoot and fix layout issues quickly.

To Apply:

Please share examples of similar Elementor header and footer fixes you have completed.

I’m looking for someone who can start soon and complete the work efficiently. There may be opportunities for future WordPress tasks if the collaboration goes well.

WordPress / Website Developer for Ongoing Ad-Hoc Website Support
Overview

We’re looking for a reliable and experienced web developer to provide ongoing website support and make updates or changes as required.

This is a flexible, ad-hoc engagement rather than a full-time or fixed-hours role. Tasks will vary depending on our needs, and there may be some weeks when no work is required.

We anticipate approximately 30 minutes to 1 hour of work per week on average, depending on the tasks and workload. Some tasks may take less time, while others may require additional hours, which can be discussed in advance.

Key Responsibilities
Make website updates and changes as requested.
Fix minor website issues, bugs and technical errors.
Update website content, images, text, links and page layouts.
Assist with basic website maintenance and troubleshooting.
Ensure the website functions properly across desktop and mobile devices.
Identify and resolve minor technical issues where possible.
Provide recommendations for improvements when appropriate.

Requirements
Proven experience in website development and maintenance.
Proficiency in WordPress and relevant website technologies.
Ability to troubleshoot issues and implement changes efficiently.
Good attention to detail and a proactive approach to problem-solving.
Reliable communication and the ability to respond to requests within an agreed timeframe.
Ability to work independently and manage small tasks with minimal supervision.

Work Arrangement
Engagement: Ongoing, as-needed support.
Estimated workload: Approximately 30 minutes to 1 hour per week on average, depending on demand.
Hourly rate: US$13 per hour.
Work availability: No guaranteed weekly hours. There may be weeks with no tasks.
Payment: Hourly, based on the time spent on agreed tasks.
Flexibility: Tasks will be assigned as needed, with timelines agreed upon based on urgency and complexity.

We’re looking to build a long-term working relationship with someone dependable whom we can contact whenever website assistance is required.

How to Apply

Please include the following in your proposal:

A brief introduction and summary of your website development experience.
Your experience with WordPress and website maintenance.
Examples of websites you have worked on, if available.
Confirmation that you accept the hourly rate of US$13 and your typical availability for ad-hoc tasks.
Your usual response time when new requests come in.

We look forward to finding a reliable developer for ongoing website support.

Title: Full Stack Engineer
Department: Innovation and Test Platforms
Reports to: Senior Project Manager
Direct Reports: NIL
Position Summary
We are currently hiring for the position of Full Stack Engineer on a 6-month contractual basis to maintain and enhance a cross-platform application that operates as both a desktop application (Electron) and a web application (React with an ASP.NET Core backend). The ideal candidate will have strong experience in building scalable and reusable UI components using React and a background in .Net Core.
Roles and Responsibilities
* Maintain and enhance a large-scale Electron and React application supporting both desktop and web environments
* Design and develop scalable features and reusable UI components using React, JavaScript, Material UI, and SCSS/CSS
* Integrate frontend applications with ASP.NET Core backend services via REST and WebSocket APIs • Debug, profile, and optimize application performance across desktop and browser platforms • Manage project dependencies and build workflows using npm and Vite
* Package, build, and deploy applications for Windows, macOS, and Linux environments
* Participate in code reviews and contribute to architectural discussions
* Support internationalization, accessibility, and responsive design requirements
* Leverage Generative AI tools to accelerate development workflows, including code generation, refactoring, debugging, documentation, and unit test creation.
Qualifications
Required Technical Skills
* React, JavaScript/TypeScript, SCSS/CSS, Html5, Material UI
* Redux or similar libraries
* Asp.net core/C#
* Web API (REST), Axios, WebSocket
* Experience with Unit testing (Jest) and knowledge in automated testing
* Experience with version control (Git) and project tracking tools (Azure DevOps/Jira)
* Good understanding of Clean Architecture and design patterns
* Strong hands-on experience using modern GenAI tools to enhancing coding speed, improving design decisions, writing documentation, and automating repetitive tasks
Nice to Have
* Experience with CI/CD pipelines, build tools, packaging and Docker-based deployments
* Knowledge of efficient transmission and processing of high-resolution images over network protocols

We're looking for an experienced WordPress and Elementor developer to convert an existing, fully designed HTML website into a professional, responsive, and easily manageable WordPress website.

The website has already been designed and generated using AI tools. We will provide the existing source files, including the HTML, CSS, JavaScript, and available design assets.

We do not need a new design. We need an experienced developer who can accurately reproduce the existing website in WordPress while building a clean, modular system that makes future updates and landing page creation easy.

Scope of Work

1. HTML to WordPress Conversion

Convert the supplied HTML/CSS/JavaScript website into WordPress using Elementor.

Maintain the visual design, typography, spacing, layout, animations, and interactive elements.

Ensure the website works beautifully across desktop, tablet, and mobile.

Preserve the intended user experience and functionality.

2. Modular and Reusable Architecture

This is one of our most important requirements.

We want a website built with reusable Elementor components so our internal team can easily create new pages without requiring custom development.

This includes:

Reusable sections and blocks for landing pages.

Global design settings for typography, colors, buttons, and other shared elements.

Reusable headers, footers, CTAs, forms, and content sections.

Page templates for commonly used layouts.

A structured component library within Elementor.

Consistent styling and design standards across pages.

For example, we should be able to create a new landing page by combining existing hero sections, content blocks, testimonials, CTAs, and forms without rebuilding them from scratch.

3. Performance and Technical Quality

Optimize the site for loading speed and mobile performance.

Use clean, maintainable code and avoid unnecessary plugins.

Ensure proper responsive behavior across common devices and browsers.

Implement basic technical SEO best practices.

Maintain accessibility best practices.

Ensure animations and interactive components perform smoothly.

4. CMS and Content Management

Make website text, images, buttons, and standard page sections editable through Elementor.

Set up appropriate templates and content structures.

Ensure our team can add, remove, duplicate, and rearrange sections easily.

Minimize reliance on custom code for everyday content changes.

5. Testing and Handoff

Build and test the site in a staging environment.

Perform desktop, tablet, and mobile QA.

Resolve bugs and visual inconsistencies before launch.

Provide a short walkthrough or recorded tutorial showing how to use the reusable components and build new landing pages.

Deliver the completed WordPress website, templates, and any custom code with full administrative access.

Ideal Candidate

We're looking for someone who:

Has extensive experience with WordPress and Elementor / Elementor Pro.

Has successfully converted custom HTML websites into Elementor.

Understands modular web development and reusable component systems.

Has a strong eye for design and can reproduce an existing website accurately.

Can work with custom CSS, JavaScript, and animations when needed.

Prioritizes clean architecture, website performance, and long-term maintainability.

Communicates clearly and works independently.

What We'll Provide

Existing website source files.

All available design assets.

Visual references of the approved website.

Access to our WordPress hosting or staging environment.

Feedback and guidance during development.

Deliverables

Fully functional WordPress website built with Elementor.

Accurate reproduction of the provided website design.

Reusable Elementor section and page templates.

Global design settings and reusable components.

Fully responsive layouts.

Optimized website performance.

Completed QA and bug fixes.

Documentation or video walkthrough for our team.

How to Apply

Please include:

Examples of at least two custom Elementor websites you've developed. We'd especially like to see examples where you converted an existing design or HTML website into WordPress.

A brief explanation of how you would approach building reusable sections and templates.

Your experience working with custom HTML, CSS, JavaScript, and animations in Elementor.

Your estimated timeline and fixed-price quote.

Whether you'll be completing the development yourself or working with a team.

Important: We are not looking for someone who will simply embed entire HTML pages into WordPress using custom HTML widgets. The finished website must be genuinely editable, modular, and manageable through Elementor.

We have additional website projects coming up and would love to establish an ongoing relationship with a reliable developer.

1. Get to know the MVP. Learn the four parts: the Parent App, the Child Device app, the Clinician Portal and our internal team console. Review the existing gap audit and decide what to fix before launch.
2. Choose how we go native. Decide how to package the apps for each store, for example React Native or Expo, Capacitor around the current web app, or Tauri or Electron for desktop. Write down the choice and why.
3. Build the Child Device app properly. Build a native Android app that can show screen-break reminders over other apps. Find the best approach on iOS, where apps can't draw over other apps. Add app pinning or kiosk mode where the store rules allow it.
4. Ship to every store. Publish on the Apple App Store, Google Play, the Mac App Store and the Microsoft Store. Handle store reviews, health-app rules, children's privacy rules and privacy labels.
5. Add freemium. Build free and premium tiers with in-app purchases and subscriptions on each store, plus billing for clinics.
6. Finish production basics. Set up push notifications, email, multi-factor sign-in for clinicians and staff, crash reporting, monitoring, backups and automatic release pipelines.
7. Protect health data. Keep our HIPAA readiness, accessibility (WCAG 2.1 AA) and privacy decisions intact as the app grows. Prepare for an outside penetration test and fix what it finds.
8. Work with clinicians. Turn clinical guidance into product rules, such as progression thresholds, and keep placeholder values clearly labelled until they are validated.

Updated a few websites with content and form to be provided.

Build a new website.

Hello there,

My website is slow in China, Can you help to check, and solve.

Thank you!


Jackie

We are hiring a senior Python engineer to take over a live production system as its sole engineer. About 75% of the work is the Python and FastAPI backend, and about 25% is building website and member-area updates from the founder's designs in plain HTML, CSS and JavaScript.

The product monitors public websites in near real time, detects changes such as new listings, availability and price moves, and sends alerts to paying subscribers through Discord and email. A web dashboard, price analytics and Stripe billing sit alongside it.

You own the whole stack, from data collection through alert delivery and billing to the pages members see, and you work directly with a non-technical founder who sets scope and priorities and provides the designs. Accuracy and speed matter most: the target is an alert within a minute of a change at the source.

### Engagement

- Remote contract, paid hourly. Include your rate when you apply.
- About 20 hours a week to start (proposed).
- Any time zone, with a weekly call during US business hours and same-day response on production issues (proposed).
- A screening call, then a paid trial of about 3 to 5 hours under NDA: one small backend fix and one design-to-page change (proposed).
- All work product is assigned to the company, and an NDA is required.

### What you will do

- **Data collection:** poll websites and APIs at high frequency with HTTP clients, headless browsers and proxy pools; manage rate limits and per-address health; keep write-on-change snapshots, detect changes and match the same item across sources.
- **Alert delivery:** run a discord.py bot and webhooks that deliver to channels, forum threads, private channels and DMs, plus email through Amazon SES and Postmark, and prove that every alert reaches every place it should.
- **Discord at scale:** rate limits, thread and component limits, roles and permissions tied to subscription state, interactive components and OAuth2 sign-in.
- **Web app and billing:** a FastAPI app and JSON API with a member dashboard, price analytics with server-rendered charts, and Stripe subscriptions with signature-verified, idempotent webhooks.
- **Website and member area:** build changes from the founder's Figma designs and written instructions in semantic HTML, hand-written CSS (responsive layouts with Flexbox and Grid) and vanilla JavaScript. There is no framework and no build step, and we are not looking to add one. Check each change in current Chrome, Safari and Firefox and on a phone, and flag gaps such as missing states, breakpoints or error messages instead of guessing.
- **Data and operations:** PostgreSQL with large, write-heavy tables, several services on Railway, CI and deploys on GitHub Actions, error tracking in Sentry, and uptime and cron monitoring with paging.

### Tools and services

- **Code and CI:** GitHub (pull requests and Actions), pytest, ruff, strict mypy, gitleaks and Docker.
- **Hosting and data:** Railway (several services, built with Railpack and Docker) and PostgreSQL with Alembic migrations, backed up nightly to S3.
- **Monitoring and paging:** Sentry (errors, performance traces and cron monitors), Better Stack (logs and uptime), Healthchecks.io (scheduled-job check-ins) and ntfy (phone paging).
- **Discord:** a discord.py bot, webhooks, slash commands, forum channels, Components V2 layouts, OAuth2 and an Activity built on the Embedded App SDK.
- **Web and payments:** FastAPI serving a JSON API and static pages in plain HTML, CSS and JavaScript, built from Figma designs; email and password, Google and Discord sign-in; Stripe Checkout, the customer portal and webhooks, in live mode.
- **Email:** Amazon SES with Jinja2 templates and SNS for bounces and complaints, and Postmark for account email.
- **Data collection:** httpx, Playwright and selectolax, with proxy pools.
- **Python libraries:** Uvicorn, SQLModel and SQLAlchemy, Pydantic v2, psycopg 3, APScheduler, structlog, boto3, PyJWT, bcrypt, cryptography, dnspython, phonenumbers, PyYAML, matplotlib and openpyxl, on Python 3.13.
- **AWS and admin:** EC2 and IAM Identity Center, 1Password for secrets and Porkbun for DNS.

### What you will work on first

In priority order:

1. Take over cleanly: get access, run the stack locally, read the docs and decision records, and ship one small fix through CI to production in your first week.
2. Prove the subscriber flow end to end on every plan, from signup and payment to Discord access and the first alert.
3. Complete data coverage: match each item across sources and keep it tracked.
4. Keep it reliable: every source and delivery path stays up, and nothing fails without an alarm.
5. Hit the speed and accuracy target.
6. Run operations: error triage, a staging environment, proxy decisions and cloud cost control.

### What you bring

Must have:

- Five or more years of production Python backend work: FastAPI, SQLAlchemy or SQLModel, Pydantic v2, Alembic and asyncio.
- PostgreSQL depth: query plans, indexing, large append-heavy tables, retention, safe migrations, and backup and restore.
- Web data collection you kept reliable in production for months: HTTP clients and headless browsers, proxy pools, rate limits, change detection and data quality checks.
- Production Discord bots with discord.py, run for real users: gateway events, interactions and components, webhooks, roles and permissions, OAuth2, rate limits and monitoring that catches silent delivery failures.
- Stripe subscriptions in live mode: products and prices, webhooks with signature checks and idempotency, cancellations and entitlement state.
- Running production on your own: GitHub pull requests, code review and Actions; Sentry (instrumentation, issue grouping, alert rules and cron monitors); and Railway or a similar platform (Render, Fly.io, Heroku) for multi-service deploys, environment variables, logs, metrics and cost control.
- Front end without a framework: semantic HTML, CSS (Flexbox, Grid and responsive layouts) and vanilla JavaScript, and turning a design into a page that works on phones and desktops.
- Clear written English and reporting backed by evidence.

Nice to have:

- Experience with marketplace or e-commerce data, such as inventory and pricing.
- Figma: reading designs, checking spacing and exporting assets. The founder supplies the designs, so no design work is expected.
- Discord Activities built on the Embedded App SDK.
- Email: deliverability on SES or Postmark (SPF, DKIM, DMARC, suppression lists) and HTML email that renders correctly in Gmail.
- Log, uptime and job monitoring (Better Stack, Healthchecks.io or similar) and on-call paging.
- Price analytics (percentiles, aggregates) and server-rendered charts (matplotlib).
- AWS (S3, SNS, EC2, IAM Identity Center).
- Secure storage of third-party credentials (encryption at rest, key rotation).
- React Native, for a mobile app that may come later but is not part of the first months.

### How we work

- Every change goes through a pull request into main and passes CI. No direct pushes to main, no force-pushes and no history rewrites.
- Tests never use production credentials or data.
- Diagnose before you fix: report findings with the evidence attached (log line, query, payload or screenshot), then propose the fix yourself.
- Estimate each task in hours with a committed date, and re-estimate before taking on new scope.
- Test the full flow yourself and send the evidence before the founder tests it.
- Send a short written update at the end of each working day.
- Record decisions: ADRs for architecture, with runbooks and the README updated in the same pull request.
- Secrets never go in code, commits or chat.
- AI coding tools are welcome, and you own every line you merge.
- Flag conflicts in a spec before writing code, and keep spend inside the agreed budgets.

### How to apply

Send:

1. A production data-collection system you built or ran: what it watched, how it stayed up and the worst failure you caught.

2. A Discord bot you shipped and a web page you built from someone else's design (links or short descriptions).

3. A paragraph on each of these:

- A site publishes a new item in one place well before it appears on the page you poll. How do you alert on it within a minute of its first appearance?

- Your system detected a change a few minutes after it happened, but the Discord alert went out half an hour after that. Where do you look first, and what do you add so it cannot happen silently again?

- A missing configuration value means paying subscribers stop receiving alerts with no error raised. How do you make that failure loud?

- Your Discord server is at 980 active threads, and a burst of new listings is about to create 60 more. What breaks, and what would you have built beforehand so it doesn't?

- A design shows a new three-tier pricing section for a page built in plain HTML, CSS and JavaScript with no framework. How would you build it so it works from a 360px phone to a desktop, and what would you check before shipping? What would break if the same markup went into an HTML email opened in Gmail?

4. Your hourly rate, weekly availability and time zone.

We run a tour company website. It is slow on mobile and fails Google's Core Web Vitals. Many of our visitors are overseas (Hong Kong, Malaysia), and the site is hosted in Tokyo.

Current PageSpeed Insights results (homepage):
- Real-user data (mobile): LCP 4.6s, TTFB 2.1s, FCP 3.7s (Core Web Vitals: Failed)
- Lab test (mobile): Performance 55, LCP 18.3s, FCP 6.9s
- Lab test (desktop): Performance 35, LCP 7.7s, Total Blocking Time 910ms

Our own investigation suggests the main causes are:
- A large hero image (likely the LCP element)
- Slow server response for overseas visitors (no CDN)
- Heavy JavaScript (page builder / slider / third-party scripts)

Before starting, please send:
1. Your diagnosis of the top 3 causes, based on PageSpeed Insights
2. Your planned fixes
3. Any costs outside this job (e.g. hosting upgrade, paid CDN or plugin). Do not purchase anything without our approval.

Acceptance criteria (job is complete when all are met):
- Mobile PageSpeed LCP under 3s on the homepage and 2 tour pages we nominate
- Mobile Performance score 80+ on those pages
- No visual or functional breakage: menus, sliders, enquiry/contact forms, and all language versions (English and Traditional Chinese) must work
- Improvements must be genuine for real users. No techniques that only target Lighthouse (e.g. hiding content from test bots).
- A written list of every change made (plugins added/removed, settings, image changes, CDN setup), so our in-house developer can maintain it

Requirements:
- Full backup or staging copy before making changes
- Proven experience with Core Web Vitals / page speed on [WordPress]. Please share 1–2 before/after PageSpeed examples.
- Work alongside our in-house developer, who will review the changes

Metric Mobile Desktop Google's "good" threshold
Core Web Vitals assessment Failed Passed —
Largest Contentful Paint (LCP) 4.2 s (poor) 1.7 s ≤ 2.5 s
Interaction to Next Paint (INP) 100 ms 48 ms ≤ 200 ms
Cumulative Layout Shift (CLS) 0.02 0.08 ≤ 0.1
First Contentful Paint (FCP) 3.5 s (poor) 1.6 s ≤ 1.8 s
Time to First Byte (TTFB) 2.1 s (poor) 1.4 s (needs improvement) ≤ 0.8 s

Platform
WordPress on managed hosting with a full-page edge cache in front; the front end is built with two page builders plus several add-on packs.
Layer What's in use
Hosting Cloudways (managed), Tokyo region, PHP 8.2, Varnish on
Object cache Object Cache Pro + Redis, active and licensed (installed manually, not via the Cloudways toggle)
CDN Cloudflare Enterprise via Cloudways: Edge Page Caching, Early Hints, Polish (lossless), WAF, rate limiting
Theme Betheme + child theme
Page builders Elementor 4.3 + Elementor Pro 3.35 (landing pages and some pages); WPBakery 7.9 (largely tour pages, most of the pages in the site)
Builder add-ons Ultimate Addons for Elementor, Element Pack Pro, Ele Custom Skin, Smart Slider 3
Multilingual Polylang: English, Simplified Chinese, Traditional Chinese
Optimisation plugins Asset CleanUp, Breeze, Async JavaScript, EWWW Image Optimizer
Other front-end Contact Form 7 + Cloudflare Turnstile, MonsterInsights (GA), social and TripAdvisor embeds


Budget: USD $150 fixed price.

Senior UX/UI Designer
Job type: Full-time
Location: Remote

About the role
We're hiring a Senior UX/UI Designer for an established company in the online trading space. Their funded-trader platform serves tens of thousands of active users across multiple regions and processes trader payouts every month.
This is a live, revenue-generating product — not a greenfield build. The company has outgrown its current design capacity and needs a senior designer to own both halves of the experience:
The product — a trader dashboard built on live market data. Account performance, equity curves, P&L, drawdown tracked against hard rule limits, payout history, trading journal, evaluation progress. Dense, numeric screens that users check several times a day and make financial decisions from. Alongside the trader, there are affiliate and internal admin views on the same system.
The web presence — the marketing site and landing pages where a visitor decides whether to buy. Pricing, plan comparison, rules, academy content, payout proof, FAQ. Revenue depends directly on how well these pages convert.

The platform operates in English and German, runs on a dark interface, and sees heavy mobile traffic.

Responsibilities
Trader dashboard & account portal
Design the evaluation progress view — profit target, max daily loss, max overall drawdown — across healthy, warning and breached states
Design equity curve, P&L, win-rate and trade-history views that remain readable from 20 to 2,000+ trades, with date-range, symbol and account filtering
Design the payout flow end to end: eligibility → request → profit split → processing status → history
Design the trading journal and calendar for fast session review
Design multi-account switching for users holding several account sizes and phases simultaneously
Design onboarding and KYC states: pending, rejected, resubmit, approved

Affiliate & internal views
Design the affiliate dashboard: referral links, click-to-conversion funnel, commission accrual, payout history
Design internal review screens for account checks, breach review and payout approval
Maintain one shared component layer across trader, affiliate and admin rather than three parallel designs

Marketing site & conversion
Design plan comparison across multiple programme types and account sizes
Design the checkout path from plan selection to payment, and reduce drop-off
Design rules, FAQ and academy pages for genuine readability
Specify and design A/B variants on revenue pages; iterate from analytics data

Design system & handoff
Build and maintain design tokens, type scale, spacing, chart palette, component variants and states
Theme light/dark through Figma Variables — one source, not two maintained files
Build in Auto Layout so German strings (~30% longer than English) don't break layouts
Hand off via Figma Dev Mode with annotations, redlines and specifications
Run design QA on staging before release

Required skills & tools
Design & prototyping
Figma — expert level: Components, Variants, Auto Layout, Variables, Dev Mode · Interactive prototyping · FigJam · Adobe Creative Suite or equivalent

Design systems
Design tokens · Atomic Design methodology · Component libraries with documented states · Multi-theme (light/dark) and multi-locale architecture

Data & dashboard design
Information hierarchy for numeric data · Data visualisation: line, candlestick, bar, area, distribution · Table design with sorting, filtering, pagination and bulk actions · Chart state design: empty, loading, no-data, partial, error

Web & conversion
Responsive, mobile-first web design · Landing page and funnel design · Conversion rate optimisation (CRO) · A/B testing methodology · Working knowledge of Google Analytics 4 and Hotjar or Microsoft Clarity

Research & validation
User flows · Information architecture · Wireframing · Usability testing · Heuristic review

Technical literacy
HTML / CSS fundamentals — enough to brief and review implementation · Responsive breakpoints and grid systems · WCAG 2.1 AA contrast, particularly in dark UI · Internationalisation (i18n) constraints

Collaboration
Jira or Linear · Slack · Notion or Confluence · Agile/sprint delivery · Written design rationale and specification

Experience required
5+ years in product/UX design, including at least 2 years on data-dense B2C or B2B SaaS
At least one shipped product where users read live or frequently-changing numbers and act on them — trading, analytics, finance, logistics or monitoring
At least one marketing site or landing page where conversion was measured, with results you can state
At least one design system you built or extended that other designers and engineers worked inside
Portfolio containing 2–3 case studies that show process, not only final screens
Professional written English (B2 or above)

Nice to have
Fintech, trading, brokerage, crypto, investment or banking product experience
German language ability (A2+)
Familiarity with MT5, cTrader, TradingView or similar charting interfaces
Webflow or Framer — able to ship marketing pages directly
Charting library awareness: TradingView Charting Library, Highcharts, Recharts, ApexCharts
Storybook familiarity for design-system handoff
Motion and micro-interaction design: Principle, ProtoPie, Rive or Figma Smart Animate

Need a Mailchimp expert to help build and refine an email template using HTML. I am creating an email template that's part of an automation triggered from a quiz created in Scoreapp. The original code that was created worked when it was tested, but once the content of the code was updated it no longer works and comes out blank on the actual email for that section. Coding structure was kept the same, only the content was changed, so I require someone to fix this issue.

I need installation of a simple ecommerce template theme with admin panel in my server through ftp.
This is a quick work and need it done quickly. 

Skills: HTML, FTP, WordPress, Web Servers, Web Hosting, Back End Development, Admin Panel, Front End Development

Develop a Service Providers section on our app’s Home Screen that displays only approved providers who applied through our website. Admin must be able to review applications, accept or decline providers, and manage visibility in the app. Only accepted providers should appear in the app, and the section should be integrated with our existing backend and frontend. The work includes building the admin interface for application review, updating the Home Screen display logic, and ensuring the feature works smoothly across the app.

Location: South America
Position: Full-Stack Developer / Client Communication Representative
Hourly Rate: $40 USD/hour
Start : Immediately
English Level: Native or Bilingual Proficiency

About the Role

We are looking for a motivated and communicative Full-Stack Developer to join our growing team.

This role combines technical knowledge with client-facing responsibilities. You will represent our development team, communicate with clients, understand project requirements, and help ensure smooth collaboration.

Extensive professional development experience is not required. A solid theoretical understanding of programming and familiarity with modern web technologies are sufficient.

Technical Requirements

Good understanding of React.js and Node.js

Solid knowledge of programming fundamentals

Familiarity with full-stack web development concepts

Ability to understand and discuss technical requirements

Please send me your introduction loom video (1-2mins)

Thanks.

My wordpress website is not being working properly. I need someone to figure out how to do it.

Hello,

We are after someone that is skilled in the following

Web Design
WordPress
PHP
HTML5
CSS3
Ecommerce

We require someone to make changes to our customer websites and our own internal websites this could be editing current pages or adding on new pages,

We require someone that is skilled in web design and designing homepages, editing logos content

We require someone that can work full time 40-60 hours a week we require someone that works fast and gets the job done and who can handle muiple jobs

We also have interna Customer Helpdesks as well that was designed in PHP framework we do have some updates in that as well that need to be maintained

I need someone to build 3D Animation for my Jewerly site, its a quick task, looking for someone whos available right now.

Hello!

I'd like to invite you to take a look at the job I've posted. Please submit a proposal if you're available and interested.

https://repair.mbgapplianceservices.com/

i'm looking to redesign this website..? make it SEO and AI optimized..

I need some help Setting up my shopify site and there have been a few bugs on functionality, inventory and the UX. I´d need the designer to do an audit and then fix.

Prepared for: Slava
Prepared by: Justin Winch, Winch Law Firm, LLC
Date: 10/15/2026
Purpose: Architecture review of existing Power Platform matter management system, and recommendation for remediation and future build.

1. WHO I AM AND WHAT THIS IS

I am a Louisiana attorney with a niche practice in expropriation and physical property damage litigation. Ten years in practice. Solo/small firm. I handle two basic case types:
1. Property damage cases — plaintiff-side, Louisiana state court.
2. Expropriation cases — representing landowners against taking authorities (e.g., Entergy transmission corridors, including the Babel-to-Webre project).
I have built a working but structurally flawed matter management system on Microsoft Power Platform. I need a senior architect to zoom out, diagnose the system as a whole, and recommend a remediation roadmap — not to write more flows on top of what exists. I am hiring you for your judgment, not your hands.

Design principle that drives everything:"The failure point is the moment of entry. Everything downstream must be a consequence of that moment, not a separate act of memory."
This comes from a real event. In 2019, I missed a prescription date. It resulted in a $60,000 malpractice settlement and a disciplinary matter that I am still dealing with. The system I am building exists to make that failure mode structurally impossible — not by trying harder, but by removing the human memory requirement from the critical path.

Scope of this engagement: Architecture assessment and written roadmap only. I will hire a separate builder for implementation based on your recommendations.

2. CURRENT SYSTEM — WHAT EXISTS

Platform Stack
• Dataverse (primary data layer)
• Model-Driven Power App — "Winns Law Firm Matter Management" (note: "Winns" vs. "Winch" — verify the correct spelling in the app name and environment)
• Power Automate — multiple flows
• SharePoint — document storage, one folder structure per matter
• Microsoft Forms — intake questionnaires
• AI agents (external, via API/OpenAI/ChatGPT) — petition drafting, discovery drafting
• Netlify — hosting for external landing pages
• Google Search Console + Google Analytics 4 — SEO/analytics layer (separate workstream; not part of this engagement)
Core Table: matters
• Currently 84 columns
• I understand this is the primary structural problem
• Many columns appear to be case-type-specific fields that should live in child tables
• No clean Status choice column exists — stage information is trapped inside Business Process Flow plumbing
Business Process Flows (BPFs)
• Two BPFs exist: Pre-Litigation and Litigation
• I built them because I wanted a visual pipeline view of all active matters by stage
• I now understand BPFs are per-record only — they do not produce a dashboard of all matters side-by-side
• I do not want to keep the BPFs as the stage-tracking mechanism. I want a plain Status choice column on matters, driven by Power Automate flows, that feeds a dashboard.
Active Data
• ~17 active matters with real client data. Cannot be lost.
Current Workflow (as it actually operates today)

This is the workflow, in sequence, for a property damage case:
1. Client interview — conducted via Microsoft Forms questionnaire + recorded phone interview.
2. AI agent pulls a markdown file containing Louisiana petition-drafting rules (references to Louisiana Code of Civil Procedure, caption format, signature block, example pleadings).
3. AI generates the petition from the intake data.
4. Second AI agent generates matching discovery so petition and discovery can be served together (Code of Civil Procedure permits discovery to be served with the petition).
5. Service — manual step. Must be done through Clerk Connect (Louisiana e-filing/serving portal).
6. Clerk Connect confirmation email arrives with conformed copies.
7. Incoming email triggers a calendar flow — sets a deadline 31 days from service (Louisiana answer deadline).
8. Follow-up workflow initiates on that timeline.
The same general architecture applies to expropriation cases, with different pleadings and different timing rules.

E-Filing Document Pipeline

Every time I e-file, I receive an email from the e-filing vendor containing an HTML table with links to court-stamped PDF copies. The flow needs to:
• Parse the HTML table to extract the document URLs
• Fetch each PDF from its URL
• Save each PDF to the correct SharePoint matter folder
• Use a consistent naming convention tied to the matter number and document type
• Log the document in Dataverse
I understand there are multiple ways to build this. I want the tightest version — the one that survives vendor email template changes and handles multiple attachments without dropping any.

Landing Page → Dataverse Pipeline (connected workstream)
• External landing pages (hosted on Netlify, subdomains like entergybabelwebre.winchlawfirm.com) collect intake information from prospective clients
• Form submissions need to feed into Dataverse and create the corresponding matter row + SharePoint folder structure
• This is the receiving end I need from you — the web/SEO side is separate and handled elsewhere
Known Web-Side Issues (for context, not part of this engagement)
• HTTP vs. HTTPS duplicate indexing across root domain and subdomains
• Google Search Console reporting "Duplicate, Google chose different canonical than user"
• Landing page subdomains not fully indexed
• These are being handled separately. Mentioning only so you understand the full system.

3. WHAT I NEED FROM YOU

A written assessment and remediation roadmap, delivered within 3–5 business days of your review.

Deliverables (required outputs — not optional)

1. Written Architecture Summary (1–2 pages)

Covering:
• Recommended data model (what stays on matters, what moves to child tables, what gets deleted)
• Recommended approach for status tracking (plain Status column vs. BPF — and why)
• Recommended flow architecture and triggers
• Key design decisions and the reasoning behind them
• Any assumptions or dependencies
2. Flow Index

A list of every flow in the system (existing and recommended), including:
• Flow name
• Trigger
• Target tables
• Connectors used
3. Assumptions and Dependencies List

Things the system depends on that could change or break — e.g., "this flow assumes the e-filing vendor sends emails in [format]."

Questions I Want Your Judgment On
1. Data model. Of the 84 columns on matters, what should stay, what should move to child tables (parties, events, documents, correspondence), and what should be deleted?
2. Status tracking. Given that I want a dashboard of all active matters by stage, what is the right architecture? I lean toward replacing the BPFs with a plain Status choice column driven by flows. Do you agree?
3. E-filing flow robustness. The current flow parses HTML from vendor emails. Is it built tightly enough to survive template changes? What would you change?
4. What I'm missing. Based on your experience with professional-services or matter-management systems, what standardized processes or automations should exist that I haven't built?
5. Sequencing. What should be done first, what depends on what, and what is the rough effort estimate for each item?
What This Engagement Is NOT
• Not a full system rebuild
• Not an open-ended discovery call
• Not a coding project — I am buying your analysis and your judgment
After This Engagement

Once I have your roadmap, I will hire a builder to implement it. I would be open to you being that builder, or to you recommending someone. Either way, the roadmap is the deliverable from this phase.

4. WHAT I'LL BRING TO THE CALL
• This briefing document
• The full 84-column list for the matters table
• A screenshot or walkthrough of the two BPFs
• One real e-filing confirmation email (redacted as needed) showing the HTML table format
• A walkthrough of the SharePoint folder structure for a matter
• A live look at the landing page form and what fields it collects
• The existing workflow description (Section 2 above)

5. ABOUT CONTINUITY

I am looking for an ongoing relationship, not a one-off. My practice is growing, and the system will need to evolve. If this engagement goes well, I would want to discuss:
• A retainer or priority arrangement for future work
• A standing rate for maintenance and additions
• Documentation durable enough that a future developer could pick up the system if you were ever unavailable
I mention this upfront because I want you to know I am not shopping for the cheapest one-off. I am looking for the person who builds the foundation I will rely on for the next 20 years.

6. REQUIRED QUALIFICATIONS (FOR MY OWN REFERENCE)
• Hands-on Dataverse data modeling (tables, relationships, child tables, choice columns vs. lookup tables)
• Experience refactoring over-columned Dataverse tables
• Understanding of when BPFs are the wrong tool
• Comfortable evaluating existing Power Automate flows for robustness
• Bonus: experience with legal, professional-services, or matter-management systems

End of briefing. Please review before our call.

We are looking for a senior AI automation engineer or a small, experienced team to build an integrated e-commerce operating system.

This is a hands-on implementation project—not a strategy presentation, chatbot or collection of disconnected automation demos.

We want to start as soon as possible. Propose your fastest realistic delivery schedule, with fixed prices, clear milestones and measurable acceptance criteria.

THE GOAL

Build a system that continuously:

Researches products → prepares stores and offers → creates marketing assets → runs approved advertising → publishes organic content → handles community interactions → measures results → improves the next round of decisions.

One human approves key decisions through WhatsApp. Routine actions execute automatically within approved rules, permissions and spending limits.

The system must record what it recommended, why, what was approved, what it executed and what happened afterward.

We have a detailed specification of approximately 50 pages to share before the final scope and price are locked.

PHASE 1: 14 FUNCTIONAL ROLES

1. Product Scanner
Collect signals from approved sources such as Winning Hunter, accessible Meta advertising signals, TikTok Shop, search trends and reviews. Produce scored opportunities with sources, timestamps and clearly stated uncertainty. Do not invent unavailable competitor metrics.

2. Deep Researcher
Investigate shortlisted products in parallel: customer problems, reviews, demand, competition, suppliers, delivery assumptions and potential margins. Present the top three opportunities for human approval.

3. Store and Offer Builder
Use our approved Shopify template to prepare product pages, offers, bundles, FAQs, emails and product images. Work within authorised stores. Identify any store-provisioning or account-setup steps that require manual action.

4. Store QA
Check mobile layout, agreed performance targets, variants, pricing, inventory, checkout per target market, pixels/CAPI and unsupported claims. Create a short approval card before publication. Block launch when required checks fail.

5. Media Buyer
Execute configurable Meta advertising rules: testing, scaling, cost caps, broad targeting, existing post IDs, winner selection, kill thresholds and budget adjustments. Include minimum-data requirements and cooldowns. Rules must be in configuration, not buried in code.

6. Creative Writer
Generate scripts, hooks, headlines, ad copy and static-ad concepts based on product facts, approved positioning and previous results.

7. Creative Producer
Generate or render approved images, AI-UGC and voice assets through selected providers. Handle formats, versions, approvals and uploads. No fabricated customer testimonials or unsupported product claims.

8. Marketing Auditor
Independently check proposed and executed marketing actions against permissions, spending ceilings and policy rules. Detect unexpected changes, pause unsafe activity and reverse supported changes where appropriate.

9. Performance Analyst
Collect and reconcile hourly advertising, store and profit data. Report spend, orders, revenue, acquisition costs and margin using agreed definitions. Distinguish platform-attributed conversions from observed store orders.

10. Organic Publisher
Repurpose approved winning creatives, schedule content and track links and attributable orders per post. The target architecture should support 10–20 authorised accounts per agreed platform. State exactly how many accounts and which platforms your Phase 1 quote includes.

11. Community and Inbox
Process accessible comments and DMs across the agreed channels into six buckets: product questions, purchase intent, order/delivery questions, complaints/returns/refunds, positive or neutral engagement, and spam/abuse.

Answer appropriate messages from an approved fact sheet. Escalate complaints, sensitive account issues and uncertain cases. Do not blindly reply to everything or invent answers.

12. Cash and Learning
Refresh spending allowances hourly using available balances, reserves, committed costs and runway assumptions. Enforce shared allowances before spending increases.

Run a nightly review that updates product and creative rankings and proposes rule changes. The system may not independently rewrite its safety limits or expand its spending authority.

13. Orchestrator
Manage schedules, queues, dependencies, product/country state, retries and recovery. Send WhatsApp approval cards, concise digests and urgent alerts. Approvals must identify the exact action, target account, amount and expiry.

14. Reserve Auditor
Provide an independent second check for higher-risk actions across departments. This role cannot approve its own proposed actions or override the human’s limits.

ARCHITECTURE AND SCALE

These are 14 functional responsibilities, not a requirement for 14 separate applications or model calls.

Use the simplest maintainable architecture that delivers the agreed behaviour. Deterministic code should handle calculations, permissions and enforcement; AI should handle tasks that actually benefit from it.

Independent tasks must run in parallel per product and country. Dependent actions must still wait for the required data, QA and approvals.

Phase 1 must prove the full workflow on a controlled initial product/market setup and demonstrate isolated parallel execution across 10 product/market jobs. We are not asking to launch 10 paid campaigns simply to test concurrency.

Phase 2 will expand capacity or split responsibilities only where operational results show a bottleneck. Do not move the core Phase 1 roles into Phase 2 without explicitly agreeing this.

PREFERRED STACK AND INTEGRATIONS

Python/FastMCP, Postgres, Redis and Docker.

Shopify Admin GraphQL, Meta Marketing API, TrueProfit, relevant payment/balance sources, Klaviyo, TikTok, Google Drive, AI-UGC/voice APIs and WhatsApp Business API.

Alternatives are welcome where they reduce cost or complexity without weakening reliability, ownership or functionality.

Before implementation, identify the supported integration route, required permissions, approval dependencies and costs for every provider. No silent substitutions, undisclosed manual steps or promises based on API access that has not been checked.

Validate TikTok publishing feasibility specifically. Propose an approved provider or a clearly identified human step where required. Do not build around bypassing platform restrictions.

SAFETY AND DATA REQUIREMENTS

All money-changing actions must pass central permission and budget checks. Parallel workers must not each spend the same remaining allowance.

Use versioned rules, authenticated approvals, duplicate-action protection, bounded retries, rate-limit handling, monitoring and a global kill switch. Reject expired or replayed approvals.

Missing or stale financial data must block spending increases. Document platform reporting delays and any limits on how quickly external campaigns can actually be stopped.

Payment/balance integrations are read-only unless a specific write action is separately authorised. Autonomous bank transfers, supplier payments and refunds are outside the default scope.

Do not persist raw customer names, addresses, emails, phone numbers or message bodies in the agent database or logs. Keep customer records in their source platforms. Document and obtain approval for any necessary identifiers or temporary processing, and redact customer details before model calls.

Treat scraped pages, reviews and incoming messages as untrusted content, not instructions that can override system permissions.

PROPOSED MILESTONES

M1 — Paid pilot and integration validation
One Shopify store and one Meta account running collect → recommend → approve → execute. Demonstrate one agreed low-risk action, rejection handling, audit logging and duplicate-action protection.

The reference pilot budget is $800, with a target of one week after the required access is available. Confirm feasibility or explain the specific adjustment you propose. This is not the total project budget.

M2 — Research, store and offer workflow
Demonstrate sourced product scoring, parallel research, shortlist approval, a generated product page, QA checks and controlled publication.

M3 — Creative and paid marketing workflow
Demonstrate creative generation and upload, configured advertising rules, hourly analysis, independent auditing and budget enforcement.

M4 — Organic and community workflow
Demonstrate publishing through the agreed supported channels, tracked links, the six inbox categories, fact-based responses and human escalation.

M5 — Integrated operation and learning
Connect all 14 roles, demonstrate parallel product/market execution, hourly cash controls, nightly learning, WhatsApp approvals and recovery from integration failures.

M6 — Acceptance, deployment and handover
Complete the agreed monitored test period, resolve acceptance-blocking defects and deliver the deployment, source code, configuration, tests, documentation and operating instructions.

You may propose a better milestone structure, but every Phase 1 requirement must map to a named deliverable. Clearly distinguish developer-controlled delivery dates from external approval dependencies.

WHAT COUNTS AS DONE

Each milestone needs a written test plan agreed before work starts.

The final acceptance tests must demonstrate:

- A complete approved product-to-marketing-to-results workflow using real integrations in our environment.
- No execution of rejected, expired or unauthorised actions.
- No duplicate external action when a webhook, job or approval is replayed.
- Correct isolation and shared-budget enforcement across concurrent jobs.
- Blocking and alerting when required financial data is stale or unavailable.
- Working pause controls, retry handling and documented recovery behaviour.
- Hourly reporting, nightly review and traceable decision/action logs.
- A handover that allows another competent developer to deploy and operate the system.

Required functionality cannot be accepted on mock data alone. Test fixtures are appropriate for failure scenarios, but must be labelled.

Commercial results such as winning products or a particular ROAS are not software acceptance criteria. Correct implementation of the agreed workflow and rules is.

FIXED PRICE, PAYMENT AND SUPPORT

Fixed-price milestones only. Quote the complete Phase 1 cost, not just the pilot.

Each milestone will be funded through Upwork before work starts. Payment approval will follow successful completion of its written acceptance tests, subject to Upwork’s review and dispute procedures.

Incomplete work or reproducible defects against the agreed scope will be returned for correction. Fixing those defects is included in the milestone price. New features and scope changes require written approval and a separate quote before work begins.

Include a 30-day post-handover warranty for reproducible in-scope defects. Quote ongoing maintenance and third-party API changes separately.

Disclose infrastructure, model usage, rendering, messaging, subscriptions and other recurring charges separately from development fees. Include operating-cost estimates for the initial setup and the proposed expanded capacity.

Development must take place in our repository, with deployment under our control. Deliver custom source code, configuration, tests and documentation, and disclose third-party components and licences. Ownership of paid custom deliverables must be included.

TIMELINE AND WORKING STYLE

Start as soon as possible and propose the fastest schedule you can genuinely deliver.

Provide a specific start date, delivery date for every milestone and final completion date. “ASAP” by itself is not a timetable.

Work in small, testable releases: build → test safely → demonstrate → release → improve from real results.

Keep updates brief and useful: completed work, evidence, blockers and the next delivery date. Raise blockers immediately rather than waiting until a deadline is missed.

We value engineering judgement. Challenge unnecessary complexity and suggest cheaper or simpler approaches where they achieve the same outcome.

YOUR PROPOSAL MUST INCLUDE

1. Relevant production examples and your personal contribution.
2. Your proposed architecture and the main integration risks.
3. Fixed total price and fixed price per milestone.
4. Start date, milestone dates, final delivery date and committed team capacity.
5. Acceptance tests, required access, external dependencies and explicit exclusions.
6. Recurring operating costs, included support and anything you would simplify.

Please review the full specification before confirming your final fixed-price commitment. No unpaid custom implementation is requested; the pilot is a paid milestone.

All pre-contract discussions and all project payments will remain on Upwork. WhatsApp is part of the system we are building, not a request to move the hiring process off-platform.

We're looking for an experienced Notion and Bullet.so expert with strong website visual design skills to improve and build a modern, professional website.

The content and structure are already in Notion. We need someone who can create attractive, responsive page layouts and implement them directly in Bullet.so.

Requirements:
- Hands-on experience with Notion and Bullet.so.
- Strong website visual design and UI/UX skills.
- Ability to independently create polished designs without Figma files.
- Experience with Bullet.so customization and basic CSS/HTML.

To Apply:

Please share your relevant Notion/Bullet.so website examples, design portfolio, hourly rate, and EST working availability.