Market Research Coding Projects

opportunity

Build Integration to send IONOS Web Orders to Kipos POS

We run a food takeaway and need a developer to build an integration so that orders placed on our IONOS webstore are automatically sent into our Kipos account (https://app.kipos.uk/) and print straight to our kitchen/printer setup with no manual re-entry. This must be production-ready: fast, reliable, and built to handle busy service periods. What the integration must do 1) Capture new online orders from IONOS Detect new orders as soon as they’re paid/confirmed (or the correct “ready for kitchen” status) Pull all relevant order data: Order ID, timestamp Customer name + phone/email Delivery vs collection Address (delivery) / pickup details (collection) Requested time: ASAP vs scheduled (time slot if applicable) Customer notes (allergies, “no onions”, etc.) Items, quantities, variants Modifiers / add-ons / extras (e.g., “extra cheese”, “no sauce”, spice level) Discounts / delivery fee / tips (if present) Payment method/status 2) Create the order in Kipos exactly as the kitchen needs it Push the order into Kipos so it lands in the correct screen/queue as an online order Map all the required fields Ensure delivery/collection is correctly set and visible on print tickets Include requested time clearly (especially for scheduled orders) 3) Auto-printing to kitchen printers Orders arriving in Kipos should auto-print to our configured printer(s), or be inserted into the correct Kipos workflow/status that triggers printing. Key requirements (takeaway-specific) Modifier & note handling (critical) Must support multiple modifiers per item, and multiple items each with their own notes Preserve formatting so the ticket is easy to read during service Handle edge cases like: “No X” and allergy notes Duplicate prevention + reliability No duplicate tickets/orders if a webhook retries or the sync is re-run Retry + failure handling: Automatic retries Clear error logs Optional alert (email) if an order fails to sync Operational timing Webhook/event-driven preferred (near-instant) Polling acceptable only if webhooks aren’t available, but it must still be reliable and efficient Security Secure credential storage (environment variables/secret store) HTTPS, least-privilege access Preferred technical approach We’re open to the best implementation, but we expect this to be either: Middleware service (recommended): listens for IONOS orders and posts to Kipos or Direct plugin/integration if IONOS supports it. Deliverables Working live integration: IONOS → Kipos order creation + printing workflow Configuration options: Which order status triggers sending Item/modifier mapping method Logging dashboard or structured logs (success/failures, retries, duplicates) Documentation: Setup steps How to update menu/mappings Troubleshooting guide Test evidence: At least 10 varied test orders (modifiers, delivery/collection, scheduled/ASAP) Source code + handover (Git repo or zip) Short post-launch support period (bug fixes) Acceptance criteria A new IONOS order appears correctly in Kipos within an agreed time (e.g., under 60 seconds if webhook-based) Ticket prints automatically (or via correct Kipos status trigger) without staff interaction Items, modifiers, notes, times, and delivery/collection details are accurate and readable No duplicates under retries/network issues Clear logs for each order’s sync status To include in your proposal Your recommended approach (webhooks vs polling, architecture, hosting) Relevant experience (POS integrations, online ordering, printers/kitchen workflows) Estimated cost + timeline (phased: build → test → deploy) What you need from us (API access, sample menu, Kipos printer workflow details) Info we can provide to speed things up Sample orders (with modifiers/notes) Our current IONOS product list/menu structure Screenshot/video of our Kipos order screen + print output requirements Printer setup details inside Kipos (single printer or multiple stations)

Unreal Engine + Pixel Streaming + Full Platform Integration

We are a technical team and we handle all technical solutions and decisions ourselves. We are not looking for an architect, a planner, or someone else to define the system for us. What we need is an execution-focused engineer who can help implement the website strictly according to our requirements. This project has very strict verification requirements. There are eight platform development contracts based on the same principle; this is just the first one. We need to deliver a multi-role platform based on (state-machine driven + Stripe payments/escrow + ad bidding + 3D digital humans via pixel streaming).Using low-code + modular composition, we are building an international platform. It must be explicitly stated that this is not an MVP. A.Deployment & Infrastructure(Must be assembled and built on the Fly.io platform) 1) The platform must run on (frontend/backend, jobs/queues, WebSocket/WebRTC services as needed). 2) Proper logging/monitoring/alerting is required, including alerts for third-party integration failures and cost/usage anomalies. B.Core Requirements (Important) 1) Multi-role / four portals: end users, service providers, maintenance staff, and admin portal (different permissions and flows). 2) Critical business flows must be implemented using a state machine / state-driven architecture (no “skipping steps”): order → payment → escrow/split → fulfillment → acceptance → settlement → refund/dispute, with full traceability, rollback rules, and audit logs. 3) Payments: Stripe (payments, payouts, webhooks). Must handle idempotency, webhook replay protection, and concurrency-safe state transitions. 4) Automation / orchestration: n8n (or similar) as the workflow hub, connecting Supabase, payments, notifications, ads, and digital humans. 5) Conversational guidance: use Botpress (or similar tools) for conversations + next-step actions. 6) Advertising: creative management + delivery configuration + analytics; ad slot bidding/auction (e.g., Prebid.js / RTB model). Bidding logs must be retained and auditable. 7) Multilingual: UI/content must support multiple languages and integrate language detection and translation APIs. 8) External widgets / external entry systems：iframe / JS SDK / external components with controlled internal core logic. 9) Risk control mechanisms: rate limiting, switches, circuit breakers, fast shutdown without impacting payments) 10) 3D digital human system (Unreal Engine Pixel Streaming): 10.1.) MetaHuman + Unreal Engine for creating 3D digital humans. 10.2.) Pixel Streaming (WebRTC) to stream UE video to web/mobile clients. 10.3.) A unified control interface to switch avatars/actions and drive lip-sync via TTS audio, integrated with state-machine-driven guidance flows. C.Execution responsibility (mandatory) 1) This project must be completed independently by you personally. We do NOT accept teams, outsourcing, temporary staffing, or task splitting. 2) This requirement exists purely for commercial confidentiality reasons. 3) If the project cannot be completed by one individual, please do not proceed. D. Price and maintenance terms (fixed) Project delivery price: USD 3,000 (fixed) Post-launch maintenance: - USD 100 per month (fixed) - Includes system stability, critical bug fixes, security updates, and environment handling - No unilateral price increase is allowed - Any adjustment requires written mutual agreement If your pricing expectation is significantly higher, or if you cannot accept these terms, please do not contact us. E.Delivery time: 1) For an experienced and skilled engineer, under normal circumstances, the full project should be achievable within two months. 2) In addition, we have a clear requirement that within an earlier phase of the timeline, a runnable pilot version must be delivered. This pilot version is not the final completion, but it must already be in a stable, operable state and able to enter trial operation. 3) During the trial operation, we will identify issues, validate stability, and make necessary adjustments, so that the final delivery can meet the required quality standards. F. Please reply with: 1) Similar projects you have delivered (if possible, provide links/demos). 2) Recommended architecture and service decomposition. 3) What materials you need from me to proceed (execution step flows, required module list, etc.). 4)phased timeline, rough price range.

Advanced Webinar KPI, Revenue & Lead Attribution Dashboard

Advanced Webinar KPI, Revenue & Lead Attribution Dashboard (Google Sheets Only) Project Overview I am looking for an experienced Google Sheets data analyst / dashboard specialist to build a comprehensive, advanced KPI dashboard that tracks the full performance of my webinars — from traffic and registrations through to sales attribution by lead source and lead temperature. This is not a basic spreadsheet.
It is a multi-layer Google Sheets dashboard designed to analyse, optimise, and scale webinars profitably. This dashboard will be used by senior leadership to make decisions around: * Scaling paid traffic * Understanding where sales actually come from (warm vs cold) * Optimising webinar content, offers, and follow-up * Forecasting revenue with confidence Platform Requirement (Non-Negotiable) ✅ Google Sheets ONLY
❌ No Looker Studio
❌ No Excel-only builds
❌ No basic reporting templates The solution must use: * Structured tabs * Clear formulas (no hard-coded numbers) * Pivot tables / QUERY formulas where appropriate * Easy duplication for future webinars Dashboard Requirements 1. Traffic & Acquisition Metrics * Traffic by source (email, ads, social, affiliates, partners) * Cost per click (CPC) * Cost per registration (CPR) * Registrations by source * Revenue by traffic source * ROI by traffic source 2. Lead Source & Lead Temperature Attribution (Critical) The dashboard must clearly show where sales came from, segmented by both lead source and lead temperature. Lead Source Examples * Warm database (existing email/CRM list) * Cold paid ads * Retargeting ads * Organic social * Affiliate / partner traffic * Direct outreach / DMs Required metrics: * Registrations by lead source * Attendance rate by lead source * Conversion rate by lead source * Revenue by lead source * Revenue per registrant by lead source Lead Temperature Segmentation Leads must be categorised into: * Warm leads (existing database) * Lukewarm leads (previously engaged, non-buyers) * Cold leads (first-touch via ads) Required metrics: * Buyers by lead temperature * Conversion rate by lead temperature * Revenue by lead temperature * Average order value by lead temperature * Time-to-purchase by lead temperature This section must clearly answer: “Are webinar sales coming primarily from warm audiences, cold traffic, or a mix?” 3. Registration & Pre-Webinar Behaviour * Registration conversion rate * Registrations over time * Warm vs cold registrant split * Pre-event engagement indicators * Attendance prediction indicators (based on engagement) 4. Live Webinar Engagement * Live attendance rate * Replay views * Average watch time * Watch-time segmentation (25%, 50%, 70%, 90%) * Drop-off analysis * Engagement scoring (attendance, watch time, CTA clicks) 5. Offer & Sales Performance * Total revenue * Buyers (live vs replay) * Offer conversion rate * Average order value (AOV) * Revenue per attendee * Revenue per registrant * Time-to-purchase analysis 6. Follow-Up & Delayed Conversion * Sales from follow-up sequences * Conversion window tracking (24h / 48h / 7 days) * Revenue split: live vs post-webinar * Email-to-sale efficiency 7. Sales Call & Backend Metrics (If Applicable) * Calls booked from webinar * Call show-up rate * Close rate * Revenue per call * Webinar → Call → Sale conversion flow * Revenue by sales rep (if applicable) Executive Summary (Top of Sheet) A high-level summary tab showing: * Total revenue * Net profit * ROI * Revenue per registrant * Cost per acquisition * Revenue split: warm vs cold leads * Scale readiness indicator (Green / Amber / Red) What I Will Provide * Clear KPI definitions and formulas * Definitions for lead source and lead temperature * Sample data structure * Explanation of how data flows * Ongoing clarification during the build This project is clearly scoped and well thought through. Who I’m Looking For * Advanced Google Sheets experience * Strong understanding of funnels, attribution, and revenue analytics * Comfortable working with large datasets and complex formulas * Commercially minded (not just technical) * Clear communicator Please include: * Examples of complex Google Sheets dashboards you’ve built * How you would handle lead source and lead temperature attribution in Sheets * Estimated timeline to first working version Budget & Future Work This is an initial build, with potential for: * Automation improvements * Ongoing optimisation * Additional dashboards I am happy to pay for quality work. Question: Briefly explain how you would structure a Google Sheets dashboard to show revenue from warm vs cold webinar leads.