Mechanical Estimator Projects

Creative AI Video Producer

AI-Driven Serialized Storytelling Videos Project: Serialized Rugby Stories (AI-led) Format: Long-form storytelling videos using AI visuals, animation & VO ________________________________________ What We Need We’re looking for a creative AI video producer to bring short documentary-style stories centered around rugby players and moments to life using: • AI-generated visuals • Animated / illustrated / 2D or light 3D graphics • Stock images or footage (rights free) • Voiceover (AI or human) • Clean, cinematic editing These are story-led pieces, not social memes. We want them to be YouTube native where people watch. ________________________________________ Content Scope • Length: 3-5 minutes per story • Outputs: o 16:9 long-form (YouTube) o 9:16 for cut downs, shorts and other social channels. • Quantity: o 3 + 3 videos in initial phase o Opportunity to extend into a longer series if successful ________________________________________ Our Inputs We will provide: • Story idea & narrative direction • Script (or strong draft) • Image references or clips of real people (must resemble who is being discussed) ________________________________________ Your Responsibilities • Develop 2–3 visual treatment concepts – we will select preference of 1 to be used across all outputs. • Produce visuals (AI gen, illustration, animation or hybrid) • Source any stock • Create / source voiceover – must be highly engaging and energetic • Edit and stitch into final polished films • Deliver on time and to spec ________________________________________ Creative References (Style Direction) We’re open to ideas and ways to deliver these short stories. Here are some references • https://www.youtube.com/shorts/nW5q41-Z80Y • https://www.youtube.com/shorts/UYZ1YtvRtBY • https://www.youtube.com/watch?v=eSj80Zr6TEE • https://www.youtube.com/watch?v=JYenJVG39ZU • https://www.youtube.com/shorts/yCQrYPXkn6M These are references, not templates. We want originality based on capabilities of the tech and you. ________________________________________ Key Requirements • Visuals must clearly resemble real people (image refs provided) • Strong sense of storytelling, pacing and tone • Rugby knowledge a HUGE bonus • Confident use and owned access of AI tools (don’t mind which platform you use) • All IP belongs to us • Use royalty-free / licensed audio only ________________________________________ Timeline • Final delivery deadline: 13 February 2026 ________________________________________ When You Respond, Please Include • Relevant examples of similar work • Your suggested visual approach(es) • Estimated cost for: o 3 videos o 6 videos • Tools you typically use ________________________________________ This is an ongoing series opportunity for the right creative partner. We value taste, speed, and storytelling over gimmicks.

opportunity

Starling Business API Integration (Bulk Payments)

We run a web application that prepares bulk payments (multiple recipients, amounts, references). That part is already built. We need a developer to integrate Starling Business Bank’s native API so users with a Starling Business account can execute those payments directly from their own bank account. This is: • ✔ Bank-native API integration • ❌ Not Open Banking • ❌ Not file uploads • ❌ Not handling client money ⸻ What needs to be built 1) Connect Starling Business Account • Add a “Connect Starling Business Account” button. • Implement Starling OAuth 2.0 authorisation. • Store access/refresh tokens, account UID and category UID securely. • Allow users to disconnect/revoke access. ⸻ 2) Execute Bulk Payments When a user approves a payment run in our system: • Use the Starling Business Payments API to create payments. • One API call per payment (looped execution). • Typical runs are 10–50 payments. • Capture and store the paymentUid for each payment. • Implement idempotency to prevent duplicates. ⸻ 3) Payment Status Updates • Implement Starling webhooks for payment events. • Update each payment as paid / failed automatically. • Record failure reasons where available. • Write events to our existing activity log. ⸻ 4) Error Handling • Handle token expiry/revocation. • Handle insufficient funds and invalid bank details. • Allow retry of failed payments. • Clean fallback to manual payment if needed. ⸻ What already exists • Bulk payment preparation • Approval workflows • Manual payment fallback • Payment status models • Activity logs & notifications You are only implementing the Starling integration layer. ⸻ Deliverables • Starling OAuth connection flow • Payment initiation logic • Webhook handling • Token management • Short technical documentation ⸻ Skills required • REST APIs • OAuth 2.0 • Webhooks • Payments / fintech integrations ⸻ Important • This is not Open Banking • No CSV/file uploads • No client money handling ⸻ To apply Please confirm: • Experience with bank or payment APIs • Familiarity with OAuth + webhooks • Estimated time and cost

Need legal contract for presenting to investors of film project

I am looking for an attorney who is an expert in legal matters surrounding film funding, for commercial exhibition and distribution. I am inspired by director Sam Raimi and his team's method of sourcing investors for 'Evil Dead' (1981), by first crafting the legal contract with an attorney before approaching investors. The investors were promised a percentage of the revenue generated. I am yet unclear what the sources of generation of revenue for my project can be (ie. TV, galleries and museums, cinema theatres, video on demand?). What sets my work apart, is that I have already produced and finalised the audio track (soundtrack) of the project in the entirety, and 15 minutes of the actual film is already produced, the length of the work will be in the 40-45 minutes range. I am looking to raise 4400-4500 USD. Here is information that I was able to uncover about the preproduction and funding of 'Evil Dead' (1981), through an AI response generation platform: "before Sam Raimi (along with producer Rob Tapert and star Bruce Campbell) went out to raise money for The Evil Dead (1981), they legally structured the way they would take investments by having an attorney prepare a formal investment document. Here’s what that involved: The Legal Document They Prepared Raimi and his collaborators consulted a Detroit lawyer (Phil Gillis, a friend of Tapert’s family) to get legal advice on raising funds. Based on that advice, they formed a limited partnership — a legal entity — which became Renaissance Pictures. The attorney helped them draft a limited-partnership offering document (often called a limited partnership agreement or legal offering prospectus in that context). This document was the legal contract they would show to potential investors when soliciting funds. What the Document Contained The offering document essentially laid out the key terms of the investment opportunity: Structure of the partnership: It defined the limited partnership — Renaissance Pictures — as the legal vehicle for the project. Investment terms: It explained that the filmmakers were selling shares in the movie; they offered up to fifteen shares at $10,000 each. Escrow conditions: All investment money was to go into an escrow account that could not be accessed by the filmmakers until a minimum number of shares — nine, or $90,000 — had been sold. This was the amount they estimated they needed to begin shooting. Rights, risks, and responsibilities: It spelled out what investors owned, what risks they were taking, and the rights and duties of the partners and the investors. Return projections: Raimi and his team promised investors they could double their investment in two years — though that was essentially a projection/bluff to help attract financing. Investor communications: The plan included sending out bi-weekly newsletters on production progress and giving each investor two tickets to the world premiere. Purpose of the Document The main goal of this legal document was to: Make the offer to investors legally credible — having a formal limited partnership and a written offering made the project look legitimate rather than an informal “friends chasing a dream.” Comply with legal requirements for selling investments — even in a small independent film context, the sale of shares had to be structured to protect both the filmmakers and the investors. Set clear terms for who owned what and what investors could expect — including how and when funds could be used and what rights investors received in return. The finished legal offering document was then presented to friends, family, and local professionals (doctors, lawyers, business owners, etc.) as they attempted to raise the funds needed for production." What I practically need from you as an attorney - in the entertainment industry - is what source of revenue I can promise to my investor, in what way, and how to divide or sell, and promise the work to the investor. Ultimately creating the legal document for presentation to the investor. Thank you, looking forward to hearing from you!

opportunity

Web Designer – WordPress Site Refresh (Brand-Led, No Rebrand)

We are looking for an experienced web designer to refresh an existing WordPress website for Almost Family, a UK-based, non-medical companionship and practical support service for older people. This is not a rebrand and not a full rebuild. The objective is to align the current site to our agreed brand, simplify structure, and add a small number of new pages. ⸻ Website context • Website: www.almostfamily.co.uk • Platform: WordPress • Sector: Non-medical companionship & practical support (not regulated care) • Audiences: • Families arranging support for older relatives • Local professionals (GPs, solicitors, churches, IFAs) ⸻ Scope of work 1. Content-led refresh (implementation, not strategy) • Implement revised copy that we will provide • Ensure consistent tone across all pages • Remove or soften any language that implies regulated or clinical care • No SEO blog strategy required ⸻ 2. Page structure (already agreed) Existing pages to refresh • Home • What We Do • How It Works • Contact New pages to add • For Professionals (hub page) • Support for GP Practices • Support for Solicitors & Probate Professionals • Support for Churches & Pastoral Teams • Support for Independent Financial Advisers (All copy will be supplied or finalised with you.) ⸻ 3. Branding & logo (authoritative – important) We already have a complete Brand Guide, including: • Logo system (horizontal, vertical, mono, whiteout) • Colour palette • Typography • Imagery style This project does not involve a rebrand or logo redesign. Your role is to: • Apply the existing logo correctly and consistently • Align the site’s look and feel to the supplied Brand Guide • Correct any inconsistencies on the current site You should not: • Redesign or reinterpret the logo • Introduce new fonts • Change colours outside the defined palette • Add visual effects, badges, or marketing embellishments The Brand Guide will be provided and should be treated as the single source of truth. ⸻ 4. Design expectations • Calm, uncluttered, professional • Trust-led (not sales-led) • Not a “care agency” look • Restrained use of imagery • Mobile-friendly • Clean navigation ⸻ 5. Technical requirements • WordPress best practice • Minimal, sensible plugins only • Clean handover on completion • No ongoing marketing or SEO retainers ⸻ What we are not looking for • No rebrand • No logo work • No SEO packages • No funnels or conversion gimmicks • No ongoing retainers ⸻ Proposal requirements Please include in your proposal: • A brief explanation of how you would approach this refresh • 1–2 relevant examples of calm, professional service websites • An estimated timeline • Your proposed fee for the project ⸻ Ideal designer • Comfortable working from a clear brief • Sensitive to tone and regulated-adjacent environments • Happy implementing agreed decisions (not reinventing) • Clear communicator ⸻ Screening questions (please answer) 1. What would you not change on the existing site? 2. How would you avoid making this feel like a traditional care agency? 3. Share one example of a calm, trust-based site you’ve worked on.

opportunity

Build a learning-management + ATS + payment + blog

I am looking for a skilled web developer (or small team) to build a website similar in functionality and structure to a website that I will communicate once you are selected. The site should include: A learning-management system (LMS) / online course-portal: user registration, course catalog, video hosting or embedding, course access control, course progress tracking. User roles: learners, administrators, and possibly “applicant/recruiter” roles if needed (depending on ATS module). An applicant-tracking / recruitment module (ATS): candidate registrations, job posting page(s), application submission, admin view for applications and data, candidate database. A blog section (news / articles) — public content. Payment facility: support for international payment gateways, ability to process payments for courses or services, with secure checkout and payment notifications. User data and content security, (TLS / SSL), secure user authentication, data protection and ability to export user data. Admin dashboard for managing courses, users, content, applications, payments, reports. Scalability: site should be built on a stack that allows growth as number of users / content / traffic increases. Responsive design — mobile and desktop friendly. Preferred Technology / Approach (open to suggestions, but include): Option A (preferred if you want faster, budget-friendly delivery): Based on a well-supported CMS (e.g. WordPress) with proven LMS and ATS plugins, custom payment integration. Option B (preferred if you want scalability, flexibility, and long-term robust architecture): A custom web application (e.g. using Laravel, Django, or similar), with modular architecture for LMS, ATS, payments, blog, user management. What I need from you; Provide portfolio or examples of similar projects (LMS, membership sites, payment integration, multi-module systems, etc.) Estimate of development time and cost (if possible, with breakdown: frontend, backend, payment integration, testing, deployment) Proposed milestones/deliverables (e.g. setup, base functionality, testing, go live) Post-launch support / bug-fix policy (optional but appreciated)

opportunity

Microsoft Dynamics 365 Finance Setup and Config

We are seeking a Finance Data Migration Consultant with a strong understanding of core accounting principles and bookkeeping to set up our Microsoft Dynamics 365 Finance environment. The project involves migrating 18 months of historical data from Sage 50 and configuring specific workflows for Accounts Payable and Employee Expenses. All current historical data relates to our UK entity but we will in due course be operating accounts for UAE and Global as well which needs to be factored into the setup of Dynamics setup. Key Responsibilities 1. Historical Data Migration - Scope: Import approximately 18 months of historical records, primarily focusing on transactional data and payroll journal summaries. - Source Data: We will provide the historical data in 3 Excel files (already exported from Sage 50). You will aid in loading this data into Dynamics 365 Finance, ensuring proper dating and categorization of all opening balances and transactions. - Reconciliation: Perform comprehensive, auditable reconciliation checks between the final Sage 50 reports and the imported Dynamics 365 balances to guarantee zero data loss and absolute accuracy post-migration. 2. Functional Setup Context: We are a largely remote business and therefore require automation of entries into the ledgers in the first instance, and the ability to track invoices or expenses through an approval process – confirming the expense as a valid business expense for services received or goods received, from the correct counterparty and for the correct amount.  This needs to be done within the “system” with approvals “signatures” noted electronically within approval limits. - Accounts Payable (Invoice Management): We require a simple, lightweight approach to handle invoices for services subscribed to or products purchased. - Email Ingestion: Setup must include a workflow where invoices sent to a specific company email address are ingested/handled within Dynamics 365. - Employee Approval & Audit: We need a way for employees to either enter items (for expected invoices) or approve invoices that have come in. This must include a simple audit process to track exactly who entered or approved the expense. - Employee Expenses: Configure the Expense Management module (or appropriate workflow) to allow team members to easily upload and submit expense claims for approval Each of these categories can be served by an add-in or configuration of the stand Prerequisites - Proven experience with Microsoft Dynamics 365 Finance implementation and data migration. - Strong knowledge of Sage 50 structures to understand the source data. - Ability to configure email-to-invoice workflows (via standard D365 features, OCR, or Power Automate). Timeline - We are able to have a call to go over the requirements/deliverables if required. - Please provide an outline of your proposal to fulfil the requirements outlined above and an estimated timeline for the full process (Migration + AP/Expense Setup). e.g., 1-4 Days, 1 week.

opportunity

Graphic Charter

Brand Guidelines Development Brief The Landlord About The Landlord The Landlord is a high-end hospitality brand rooted in a refined lifestyle and a strong attention to detail. The brand operates at the intersection of hospitality, service excellence, and contemporary living. We are now entering a new phase of expansion through a franchise model, which makes visual consistency and brand clarity critical across all markets. Each franchise operates locally while carrying the same brand promise. To support this growth, we are looking to develop a complete, structured, and replicable brand guideline that can be deployed consistently across all physical and digital touchpoints. Objective of the assignment The objective is to create a comprehensive and operational brand guideline that will serve as a reference document for all current and future franchisees. This guideline must allow each The Landlord entity to express the brand with coherence, elegance, and precision, while preserving the emotional and aesthetic codes that define our brand DNA. The guideline should be practical, clear, and easy to use, enabling independent teams to apply it correctly without external supervision. Scope of work The selected agency will be responsible for designing and delivering a complete brand guideline, covering the following areas: Visual identity system Define clear rules for logo usage and placement across all supports, including: Brand extensions (TLL Franchises, TLL Manager, TLL Loyalty Program, TLL Platinum) Bedding and linen (pillowcases, sheets, duvets) Bath towels and spa linen Staff uniforms (shirts, aprons, jackets) Stationery (business cards, menus, envelopes, letterheads) Signage (storefronts, plaques, pictograms, vehicle branding) Packaging (bags, labels, boxes) Color palette Definition of primary and secondary colors Authorized shades and variations Color references (Pantone, CMYK, RGB) Recommended color combinations and contrasts Typography Primary and secondary typefaces Typographic hierarchy (titles, subtitles, body text, captions) Practical usage examples across print and digital formats Iconography and illustrations Definition of a consistent illustration style (minimal, linear, pictogram-based) Creation of an icon system covering hospitality services (reception, breakfast, spa, amenities, services) Guidelines for image and illustration treatment (line weight, spacing, visual tone) Photography direction Artistic direction (lighting, mood, subjects, composition) Storytelling approach aligned with a luxury hospitality universe Visual moodboard Image treatment recommendations (retouching, filters, grain, saturation) Examples of visuals adapted for social media, website, and printed materials Tone of voice and brand language Definition of the brand tone (warm, refined, intimate, elegant) Key vocabulary and preferred lexical fields Do’s and don’ts for brand expression Message examples for social media, email signatures, and printed materials Digital applications Design templates for: Instagram feed and stories Facebook publications LinkedIn posts and banners Layout grids and composition rules Logo, typography, and color integration guidelines Examples of carousels, stories, and short-form videos Printed materials and physical applications Complete stationery system (business cards, menus, envelopes, notebooks, labels) Uniform design guidelines and logo placement Linen and bedding specifications (materials, embroidery, positioning) Branded objects and promotional items Deliverables A complete brand guideline document (digital format) Fully structured, clear, and ready for franchise deployment Visual examples and practical use cases for each section Expected timeline and proposal We kindly ask interested agencies to provide: A detailed proposal outlining their methodology and approach A production timeline with milestones A cost estimate for the full scope of work Relevant references, ideally within hospitality, luxury, or franchise networks

opportunity

Full-Stack Mobile Developer for App (iOS & Android)

I am looking for a talented mobile app developer (or small agency) to build Pinvera, a community-driven social mapping platform. The app allows users to report and "pin" real-world social encounters to a map, categorized by specific archetypes (Karens, Chads, Legends, and Safety Warnings). The app features a robust moderation system and a gamified experience where users earn tokens, increase their trust score, and compete on a global leaderboard. Key Features & Functionality 1. User Authentication & Profiles Sign-up/Sign-in via Email, Google, and Apple ID. User profiles displaying "Trust Score," "Level," and "Total Tokens." Streak tracking (e.g., 0-day streak) to encourage daily engagement. 2. Interactive Map Interface (Core Feature) A real-time map view (Google Maps or Mapbox integration). Visual "pins" based on the category of the encounter. Filter system to toggle visibility of different pin types (Karen, Chad, etc.). "Current Location" centering and search functionality. 3. Encounter Reporting ("Add Pin") User-friendly form to submit encounters. Categories: Karen: Annoying or entitled behavior. Chad: Positive or funny encounters. Legend: Wholesome or helpful encounters. Warning: Scams, safety alerts, or warnings. Submission Details: Title, Description, Category selection, and Geo-location (automatic or manual). 4. Moderation & Pending System All submitted pins must go to a Pending Queue. Admin/Moderator capability to review, approve, or reject pins before they appear on the public map. A "Pending" tab for users to track the status of their submissions. 5. Gamification & Leaderboard Token System: Users earn tokens for approved pins. Trust Score: A leveling system (Level 1, 2, etc.) based on the accuracy and frequency of reports. Leaderboard: A dedicated "Board" tab showing top users ranked by Tokens, Trust, or Activity. 6. Categorized Feeds Dedicated tabs for "Karen Sightings," "Chad Encounters," "Nice Legends," and "Warnings." Feeds should include "Most Reported" trends for the week (e.g., "Most reported: Phone scams this week"). Technical Requirements Platform: Cross-platform development (Flutter or React Native) to ensure 100% feature parity on iOS and Android. Backend: Firebase (Firestore, Auth, Functions) or a Node.js/PostgreSQL setup. Geolocation: Deep integration with GPS and mapping APIs. UI/UX: I have existing high-fidelity wireframes/screenshots. The developer must be able to replicate the clean, modern aesthetic shown in the designs (rounded containers, soft shadows, and specific iconography). Timeline & Milestones Phase 1: Backend setup & User Authentication. Phase 2: Map integration & Pin submission logic. Phase 3: Admin Moderation panel & Pending flow. Phase 4: Gamification (Tokens/Leaderboards). Phase 5: QA Testing & Deployment to App Store/Google Play. How to Apply Please provide: Examples of previous map-based or social networking apps you have built. Your preferred tech stack for this project. An estimated timeline for an MVP (Minimum Viable Product).

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.

opportunitypre-funded

Property dispute: prepare counsel briefing notes

I am seeking a freelance UK solicitor (property litigation focus) to review a defined “core bundle” of case documents and produce a concise, legally rigorous briefing note for counsel (Direct Access). Objective • Read the core bundle and strip the matter back to its determinative legal issues. • Identify the strongest “show-stopper” points in UK property law. • Produce a clean route-map so counsel can present a short, technical argument by reference to a limited set of key documents. Deliverables 1. Core legal “essence” note (8–12 pages) o A structured route-map of the decisive issues, aligned to the Court-defined trial issues: (1) Title/status of a newly registered title and what (if anything) was enforceable pre-registration (2) Chain of indemnity / standing to enforce (benefit passing / annexation / assignment) (3) Right of way + a later deed containing the operative contribution machinery o Identify the governing statutory provisions and leading authorities for each issue (with pinpoint citations where possible). o Distil the legal tests the judge must apply, and explain them clearly in plain English tied to the documents. 2. “Show-stopper” list (1–2 pages) o Bullet list of the strongest points that defeat the claim or materially narrow it. o For each show-stopper: (i) the rule/test, (ii) the authority, (iii) the document(s) that prove the factual predicate. 3. Pleadings and proof audit (4–6 pages) o Check the operative pleading(s) against the title/deed documents and witness evidence:  what is actually pleaded;  what must be proved at trial;  what is missing (non-pleaded bases, omitted deed machinery, missing chain documents, plan/extent gaps). o Identify any procedural/candour points that properly support submissions on confinement to the pleaded case, adverse weight, and/or costs conduct. 4. Counsel briefing pack (draft-ready, 6–10 pages) o A counsel-facing note suitable to hand to counsel:  issues list + recommended order of argument;  key documents by page reference;  proposed short oral submissions on each major point;  list of questions counsel should ask and documents that must be demanded if missing. Scope and constraints • Work from the supplied “Core Bundle” only online. • UK law only: Land Registration Act 2002 (including ss.24/27 and registration gap implications), enforceability of positive covenants, benefit & burden principles, annexation/assignment/chain of indemnity, and deed construction. • Focus on clarity and authority: this must be understandable to a judge who may not engage well with abstract argument. I need crisp legal explanation tied to the documents. • This is an opinion + counsel briefing route-map, not advocacy drafting. Bundle contents (high level) • Court orders (including an order listing the trial issues) • Claim/pleadings (operative versions), defence and reply • Land Registry titles and plans (including roadway titles) • Key deed extract(s) including the operative contribution machinery • Key correspondence (including mediation-stay period correspondence) • Selected witness statements/exhibits Timescale and format • Please confirm availability to deliver within 5 working days of receiving the bundle. • Deliverables in Word (.docx) plus PDF, with a short bibliography of authorities. • Include an “assumptions/limits” section stating what documents (if any) you expected but were not provided. Commercials • I need a capped-fee proposal (ceiling agreed in advance) with an estimated hour range and your hourly rate. • Please provide two options: Option A: Essence note + show-stoppers + pleadings/proof audit Option B: All deliverables including the counsel briefing pack draft Conflict / independence • Please confirm no conflict of interest with any party/entities involved. If you are interested, please reply with: • relevant experience (property litigation, covenants, title/standing disputes, LRA 2002 issues), • proposed fixed/capped fee and delivery timeline, • any initial questions you would need answered to start.

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)

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.