Management Consulting Projects

CUPS Server-Side Release Setup

1. Base Environment Create an isolated environment for printing (dedicated VM preferred, otherwise constrained container or host service). Confirm AlmaLinux 9.x, hostname, internal DNS, and time sync. Outcome: print stack is isolated from web, mail, and Nextcloud workloads. 2. Install Core Packages Install CUPS, cups-filters, IPP support packages, and PDF utilities (e.g. poppler-utils, qpdf). Disable unused print backends. Outcome: cupsd is running and reachable locally. 3. Secure Transport (IPPS) Enable IPP over TLS (IPPS on port 631). Generate or import TLS certificates. Disable non-TLS IPP access. Restrict firewall access to trusted networks. Outcome: all printing occurs over IPPS. 4. CUPS Core Configuration Configure cupsd.conf to restrict admin access, disable unnecessary sharing, and set sensible logging levels. Define job limits (MaxJobs, MaxJobsPerUser) to avoid runaway queues. Outcome: CUPS accepts jobs securely and predictably. 5. Printer Setup Add physical printers as device queues (IPP preferred). Verify printing and media support for each printer. Apply a consistent naming convention. Outcome: all printers are reachable and functional. 6. Logical / Hold Queues Create logical hold queues (per tenant or site). Ensure jobs are held on submission and do not print automatically. Outcome: jobs reliably enter a held state awaiting release. 7. Default Printer Routing Logic Define default printer mappings per user, group, or site. Implement printer health checks. Attempt automatic release only when the default printer is healthy; otherwise leave the job held. Outcome: jobs print automatically when safe, and never fail silently. 8. Manual Fallback Release Provide a mechanism to manually release jobs to an alternative printer. Ensure jobs are either re-routed cleanly or duplicated and cleaned up correctly. Outcome: users can recover from printer failures without reprinting. 9. Release Portal Deploy a lightweight web portal. Implement authentication (OIDC, LDAP, or local as appropriate). Allow users to view, release, re-route, or delete their own jobs. Provide basic admin views for printer status and default mappings. Outcome: users self-manage held jobs securely. 10. Job Retention & Cleanup Automatically purge unreleased jobs after a short expiry window. Delete job files immediately after successful printing. Disable long-term job and file preservation. Outcome: no print data is retained beyond operational need. 11. Resource Protection Apply CPU, memory, and I/O limits to print services. Ensure print workloads cannot starve web hosting, SMTP, or Nextcloud. Outcome: other services remain responsive under print load. 12. Security Hardening Restrict access to spool directories. Enforce per-user job visibility in the portal. Prevent direct access to job content. Disallow silent automatic rerouting to other printers. Outcome: print data remains private and controlled. 13. Routing Rules (Optional) Implement routing by page size (A4 vs A3) or page count if required. Ensure routing behaviour is visible and predictable. Outcome: advanced routing works without surprises. 14. Monitoring & Health Checks Monitor queue depth, failed jobs, and printer availability. Alert on sustained queue growth or repeated errors. Outcome: issues are detected before users are impacted. 15. Validation Test normal printing, printer failure handling, manual fallback, and job expiry. Confirm no performance degradation to web hosting, mail, or Nextcloud. Outcome: behaviour matches requirements under load. Final Acceptance Statement Print jobs are securely held, released to a default printer when available, manually re-released when not, automatically cleaned up, and isolated so they do not impact other server services.

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!

PHP Developer – Booking Form & Google Maps Fare Calculator

I have a live local rideshare website built with PHP, JavaScript, and MySQL. This is a Phase 1 solo-driver MVP, not an Uber clone and not a rebuild. The site already exists. I need a developer to clean up, stabilize, and finish core logic inside the current codebase. This project is rule-driven, not feature-heavy. Scope of Work (Phase 1) 1) Ride Request Form Cleanup & Validation Clean existing form UI (no redesign) Required field validation (pickup, dropoff, date, time, name, phone, passengers) Google Places Autocomplete for pickup & dropoff Block submission unless a Places-suggested address is selected Create ride request with status Pending Confirmation page with Request ID 2) Fare Estimate Calculator (Google Maps) Use Google Directions API to calculate distance (miles) Apply pricing rules: Base fee Minimum fare Per-mile tiers Show estimated fare before submission Store distance + quoted fare in database 3) Ride Limits & Overbooking Protection Enforce: Operating hours Minimum lead time Max advance booking Daily ride cap One ride per time slot Approved rides lock the time slot 4) Admin Review & Approval Page Secure admin dashboard View requests (filter by date/status) Approve / Decline / Cancel / Complete rides Full lifecycle managed via admin UI 5) Driver Profile Page (Mobile-Friendly) Driver photo (optional) Name, vehicle info, plate number Rides completed Member since Rating (manual for now) 6) Final Polish Pricing page cleanup Airport service page cleanup + checkbox logic Clear “Request a Ride” CTAs What This Project Is NOT ❌ No framework migration ❌ No Laravel rebuild ❌ No React/Vue frontend ❌ No payments / Stripe ❌ No live GPS tracking ❌ No AI / SaaS features This is a simple, deterministic MVP. Tech Stack PHP JavaScript (vanilla or light jQuery) MySQL Google Maps / Places / Directions API Responsive HTML/CSS Budget & Milestones Total Phase 1 Budget: $280 (fixed) Milestones: Milestone 1A: Form validation + address enforcement — $40 Milestone 1B: Fare calculator + request creation — $40 Milestone 2: Ride limits + admin approval flow — $120 Milestone 3: Driver profile + page polish — $80 How to Apply (Required) Please answer all of the following: Have you worked with Google Maps Places/Directions API before? (Yes/No + brief example) Are you comfortable working inside an existing PHP codebase without rebuilding it? Confirm you understand this is a solo-driver MVP, not an Uber-style system Confirm you agree to the milestones and fixed $280 budget Proposals that do not answer these questions will be ignored. Preferred Developer PHP/MySQL focused Experience with booking or scheduling systems Comfortable following strict rules and acceptance criteria Communicates clearly and delivers incrementally

opportunity

Commercial Solar WordPress site Structured B2B Lead Gen Platform

Project Overview We are a commercial solar installer headquartered in Scotland, delivering projects across Scotland and the wider UK. The website will target UK SMEs requiring 100kWp to 1MWp installations, while demonstrating capability across larger commercial and multi-sector projects. This is not a brochure site. The website must function as: • A structured B2B lead-generation platform • The central SEO hub • A high-performance PPC destination • A corporate credibility asset for financial and procurement decision makers All copy will be provided. We require full technical build and structured implementation. ⸻ Hosting & Environment Hosting has been provisioned on WP Engine. The build will take place on staging within this environment. All domain, hosting, WordPress admin and analytics accounts will be owned and controlled by us. Developer must be comfortable working within WP Engine environments. ⸻ Scope of Work The appointed developer will deliver: • WordPress build (latest stable version) • Structured template development • ACF implementation for custom content types • Custom Solar Savings Calculator (per detailed technical specification) • GA4 + Google Tag Manager integration • Event tracking implementation • Performance optimisation • QA, staging and launch • Handover documentation ⸻ Technical Requirements (Non-Negotiable) • WordPress (latest version) • Lightweight theme only (GeneratePress, Kadence or Astra) • Gutenberg block editor preferred • ACF required for structured content • No multipurpose themes (Avada, Divi, etc.) • Clean plugin stack • Mobile-first approach • Performance-conscious build • No heavy page-builder dependency ⸻ Required Templates Reusable templates must be created for: • Homepage • Solutions page • Sector page template (ACF-driven) • Case study template (ACF-driven) • Funding options page • Resources/blog template • Solar Savings Calculator page • PPC landing page template (minimal navigation) • About / compliance pages • Contact page Templates must be scalable and editable by admin. ⸻ Solar Savings Calculator A custom interactive calculator must be built according to a detailed technical appendix (shared following NDA). Key requirements: • Native HTML/CSS/JavaScript build • No iframe embed • Admin-editable assumptions • Funding toggle (CAPEX / Asset Finance / PPA) • Results displayed immediately • Light lead capture after results • AJAX submission • GA4/GTM event implementation • Fully responsive and premium in appearance This is a structured commercial feature. ⸻ Tracking & Analytics Must implement: • Google Analytics 4 • Google Tag Manager Required events: • calculator_submit • calculator_report_request • form_submit • phone_click • CTA_click Tracking must be tested and verified prior to completion. ⸻ Performance Expectations • Optimised images (WebP) • Caching compatible with WP Engine • Clean DOM structure • No unnecessary animation bloat • Mobile performance considered • Core Web Vitals conscious build ⸻ Timeline We are seeking a quick turnaround. Target timeline: 2-3 weeks from project commencement. We are ready to begin immediately and will make prompt decisions. Applicants must confirm availability within this timeframe. ⸻ Communication & Process Requirements • NDA must be signed before full technical specification is shared. • Initial Microsoft Teams call required before appointment. • Weekly Teams check-in during build. • Staging site access required for review at each milestone. • Clear milestone approval process. ⸻ Milestone Structure 1. Architecture & Wireframes – 10% 2. Template Build – 20% 3. Calculator & Tracking – 20% 4. Performance & QA – 20% 5. Launch & Handover – 30% Final payment released only after full verification. ⸻ Required From Applicants Please include: 1. 2 relevant WordPress projects (B2B preferred) with involvement evidence 2. Confirmation of experience with ACF and Gutenberg 3. Confirmation of custom JS calculator experience 4. Confirmation of GA4/GTM event implementation 5. Your proposed theme approach 6. Estimated timeline 7. Confirmation you are comfortable signing an NDA and working via Teams Generic proposals will not be considered.

Prompt Engineer – AI Systems & Automation Specialist

I'm looking for someone who can build a solid and reliable prompting framework that delivers measurable ROI for business use cases, not just impressive demos. We need a prompt engineer who thinks like a systems architect, not just someone who can write clever prompts. You'll be designing, testing, and optimizing prompts for production-grade AI workflows. This isn't about getting ChatGPT to write poems; it's about building reliable, scalable prompt chains that solve real business problems. Deliverables What You'll Do: Design and optimize prompts for LLM-powered automation workflows (GPT-4, Claude, open-source models) Build evaluation frameworks to measure prompt performance against business KPIs Develop prompt templates and chains for multi-step reasoning tasks Document prompt engineering patterns and create reusable libraries Collaborate on agentic AI systems using frameworks like LangChain Debug and iterate on prompts when model outputs don't meet specifications Required Skills & Experience: 2+ years hands-on prompt engineering experience (personal projects count if well-documented) Deep understanding of prompt patterns: chain-of-thought, few-shot learning, system prompt architecture, retrieval-augmented generation (RAG) Experience with prompt evaluation and A/B testing methodologies Familiarity with tokenization, context window management, and model-specific quirks Strong technical writing—you can explain complex prompt logic clearly Python proficiency for prompt testing and automation integration Preferred (Not Required): Background in ML/AI fundamentals (understanding of transformers, embeddings, fine-tuning concepts), at least foundational AI/ML understanding, you don't need to train models, but you understand concepts like temperature, context windows, and model limitations. Experience with n8n, Make, or similar automation platforms Exposure to agentic frameworks (LangChain, AutoGPT patterns, function calling) In your application, please begin your cover letter with the word "CONTEXT:" followed by a one-sentence summary of what makes our AI engineering approach different based on this job description. Applications without this will not be reviewed. Assessment Task (Required with Application) Instead of multiple interview rounds, complete this practical assessment: Scenario: A client wants to automate customer support ticket classification. Tickets should be categorized into: Billing, Technical, Feature Request, or Escalation. The model sometimes misclassifies urgent technical issues as "Feature Request." Your task: Write the system prompt you would use Provide 3-5 few-shot examples you'd include Explain your reasoning for structural choices Describe how you would evaluate and iterate on this prompt Time estimate: 30-45 minutes. We value thoughtful reasoning over speed. This task reveals: Do they understand edge cases? Can they structure prompts systematically? Do they think about evaluation? AI-generated responses typically miss the nuanced "why" behind choices. What Success Looks Like Prompts that work reliably at scale, not just in demos Clear documentation that another engineer could pick up Data-driven iteration, not just "try things until it works." To Apply: Submit your assessment response and a brief note on a prompt engineering challenge you've solved. Generic applications will not be reviewed.

Webflow CMS & UX Specialist – Certification Website (5-6 Pages)

PROJECT OVERVIEW I am the Founder of Well-Being Approved (WBA), an independent certification standard for mental well-being in the workplace. WBA is being built as a long-term institutional certification body. This is not a lifestyle website or startup brochure. The build must be clean, structured, scalable, and professionally executed. I require an experienced Webflow CMS and systems-focused developer to build Phase 1 of the platform with correct backend architecture from day one. ⸻ PHASE 1 – Launch Infrastructure Scope Core Website Build (5-6 Pages) • Home • Certification Standard • How It Works • Apply • Public Directory • Contact Includes: • Institutional design (corporate, authoritative tone) • Structured hero and credibility sections • Clean typography and spacing system • Responsive optimisation across breakpoints • Professional footer Brand colours and copy will be provided. An initial AI-generated Webflow draft exists and may either be refined or rebuilt with correct architecture. ⸻ APPLICATION & PAYMENTS INFRASTRUCTURE • Multi-step structured application form • File upload capability (policy/evidence documents) • Company logo upload (for use on public directory listing upon certification) • Consent checkbox for public directory listing + rights confirmation for uploaded assets • Stripe integration for tiered application fee (based on employee band) • Automated confirmation email upon submission ⸻ DIRECTORY ARCHITECTURE A public “Certified Organisations” directory must be built. Architecture requirements: • Webflow CMS front-end • Airtable backend as internal control database • Internal vs public field mapping • Directory updates dynamically via Airtable integration Public fields • Company name • Logo (uploaded by company) • Website URL • Certification status (Certified / Pending / Suspended / Expired) • Certification date • Expiry date • Certificate ID • Sector Internal-only fields (Airtable only) • Employee band • Assessment notes • Risk flags • Submission documents • Internal payment tracking ⸻ RENEWAL & PAYMENT LOGIC (IMPORTANT) Payment structure • Application fee paid at submission (Stripe) • Assessment & verification fee invoiced post-eligibility review (manual Stripe invoice acceptable in Phase 1) • Annual certification licence fee payable only upon successful certification approval Renewal lifecycle requirements The platform must support an annual renewal process including: • Structured renewal declaration form + updated document upload • Automated renewal reminders (60 / 30 days pre-expiry) • Status management logic (Certified / Renewal Pending / Expired) • Renewal must be reviewed and formally approved before the annual licence fee is charged. Preferred approach: • Annual certification fee is handled through Stripe using a stored payment method and a reactivated annual charge triggered only once renewal is approved (e.g., reactivating a paused annual Stripe subscription or triggering an approved invoice). • Renewal form must include a clear acknowledgement checkbox confirming the annual fee will be charged upon renewal approval. No client login portal required in Phase 1. Future expansion may include secure client dashboards and renewal portals. ⸻ TECHNICAL EXPECTATIONS • Clean, organised Webflow class naming • Proper CMS structure • Airtable integration (Zapier / Make acceptable) • Stripe configuration • Scalable architecture (not hard-coded shortcuts) • Clear documentation of setup • Clean handover documentation and clear explanation of backend structure ⸻ UX JOURNEY Credibility → Understanding → Trust → Application → Payment Comparable positioning reference: B Corp (tone and institutional structure only – no duplication). ⸻ WHAT I’M LOOKING FOR • Strong Webflow portfolio (live links required) • Experience with CMS-based builds • Experience integrating Stripe and Airtable • Systems thinker (not just visual design) • Clear communication • 4–6 week delivery window ⸻ BUDGET Please provide a realistic fixed quote for Phase 1 build. This is Phase 1 of a long-term certification platform. Ongoing work likely for future expansion (client portal, automation scaling, enhancements). ⸻ If you build clean systems and think long-term, we will work well together. Preferred communication: I am available for quick feedback via WhatsApp for alignment where helpful. Phone calls are also fine.

Project Digitise

We are Citipost Mail (Citipost Ltd), a UK-based B2B mail and communications provider, seeking an experienced developer (or small team) to build a secure, end-to-end digital customer onboarding portal and workflow for new business accounts. Currently, our process is manual and paper-heavy, using multiple documents: standard Application for Credit, Agency Application Form (for Royal Mail tri‑party agency agreements), Customer Service Agreement (CSA – full and form-only versions), CSA T&Cs, and Direct Debit (DD) mandates. The average onboarding time from sending the Application for Credit to receiving the signed CSA is around 15 days for standard accounts, and we want to significantly reduce this through automation, better UX, and tighter workflow control. The new solution should move this entire process online, covering: guided form completion, document upload, e‑signatures, internal approvals, and system updates. It must support both standard and agency accounts, with conditional logic to show only relevant fields and documents (e.g. agency-specific questions and Royal Mail‑related data, or DD mandate only when DD is selected as payment method). ​ Key functional requirements: Customer-facing onboarding journey: Sales triggers onboarding, generating a secure, unique link for the prospect. Prospect completes an online form (standard or agency), uploads supporting documents (company letterhead, DD mandate, etc.), and e‑signs where required. Ability to save progress and resume, with clear, accessible UI and validation for critical fields (e.g. company registration number, postcode, bank details). ​ Workflow and internal approvals: Automatic routing of submitted applications to Credit Control for checks and setting credit terms. Generation of the correct CSA pack (full CSA + T&Cs, or CSA form with online T&Cs link) plus DD mandate, ready for customer e‑signature. Internal counter‑signature flow for Commercial/Legal, with status tracking from “Onboarding” to “Active” once fully signed and approved. ​ Automation, dashboards and reporting: Configurable email reminders for incomplete forms and unsigned CSAs/DDs, including escalation options when SLAs are breached. ​ Internal dashboards for Sales, Credit Control, and Support to view onboarding pipelines, live status, bottlenecks, and overdue tasks. Basic analytics and reporting on KPIs such as average onboarding duration, drop‑off points, and rate of returned/signed agreements. ​ Data, integrations, and compliance: Capture all existing form data (company details, trading/registered addresses, VAT, contacts, services required, anticipated spend, agency flags, payment terms/methods, etc.) in a structured database. Role-based access control and full audit trail of submissions, approvals, comments, and document versions for governance and compliance. ​ GDPR-compliant data handling, encryption in transit and at rest, and alignment with UK data standards. ​ Ability to integrate (via APIs) with our CRM (e.g. Salesforce), finance system (e.g. Sage), and internal platforms to avoid double entry and keep records in sync. Administration and scalability: Admin interface to manage and configure form fields, workflows, approval steps, email templates, and SLAs without requiring code changes for routine updates. ​ Scalable architecture and flexible design to support future onboarding volumes and potential internationalisation or additional product lines. ​ Deliverables: Technical discovery and proposed architecture/tech stack. Design and build of the onboarding portal (front-end and back-end). Implementation of agreed integrations and e‑signature solution. Reporting/dashboard setup for core onboarding KPIs. Documentation, knowledge transfer, and admin training. ​ What we’re looking for: Proven experience delivering secure B2B onboarding or workflow portals with multi-step forms, approvals, and e‑signatures. Strong understanding of data security, GDPR, and role-based access models. Experience integrating with CRM/finance systems and e‑signature platforms (e.g. DocuSign, Adobe Sign, etc.) is highly desirable. UK-based, or very familiar with UK data protection and compliance requirements. When responding, please include: Examples/links to similar portals or workflow systems you have built. Your proposed tech stack and approach for this project. Estimated timeline and ballpark budget for an MVP aligned to the scope above.

Email Marketing Campaign B2B

Hi, I’m looking for an experienced and results-driven email marketing freelancer to create and manage a targeted B2B outreach campaign for UK Wholesale. About Us
UK Wholesale is one of the UK’s largest independent wholesalers, trusted by businesses nationwide for over 20 years. We supply thousands of essential products across every category — including cleaning and janitorial supplies, industrial equipment, packaging, polythene, carrier bags, stationery, paper products (including HP paper), health & beauty products, and much more. We are official distributors and brand partners for major global manufacturers. By dealing directly with brands, we cut out the middleman and offer: * True wholesale pricing * Better-quality, fresher stock * Competitive product ranges * Fast service and reliable delivery We operate from our large Midlands distribution centre with strong stock levels and consistent availability. Campaign Focus – Leicester Only (Phase 1) This campaign must target businesses based specifically in Leicester. We are not concerned about company size — small, medium, or larger businesses are all acceptable — as long as they are legitimate businesses operating within Leicester. We do not want major national chains like Tesco or large corporations with fully centralised procurement teams. However, strong regional or multi-location businesses with local decision-makers are fine. We genuinely do not mind what type of business it is — if they operate as a business or trade in Leicester, we are happy to supply them. Preferred High-Potential Sectors * Independent retailers * Online retailers * Amazon sellers * Market traders * Pharmacies (especially strong opportunity for wholesale health & beauty products) * Offices and corporate offices * Solicitors and law firms * Accountants * Recruitment agencies * Janitorial companies (we supply wholesale cleaning products) * Care homes * Nurseries * Manufacturing companies * Engineering firms with warehouse/industrial units * Industrial estate businesses * Corporate offices * SMEs * Schools & universities * Healthcare providers * Government departments * Warehouses & distribution centres * Leisure Centres * Private Gyms * Golf clubs * Supermarkets PLEASE DO NOT SEDN THIS CAMPAIGN TO WHOLESALERS, DISTRIBUTORS, CASH & CARRYS, PACKAGING COMPANIES. Other than the above If they run a business, we can supply it. The Objective of the Email The email must be extremely professional, persuasive, and enticing. This is not just an introduction email — it must drive action. The goals are: 1. Get them onto our website 2. Encourage them to place their first order 3. Position us as a better alternative to their current supplier 4. Establish us as a long-term supply partner Key Selling Points to Highlight * Low minimum order – just £99 * Free UK delivery * Thousands of products in stock * Fast dispatch from our Midlands distribution centre * Strong stock availability * Official brand partnerships * £10 off their first order * Flexible payment options: * Bank transfer after goods are received and checked * Pay by card on delivery * Business credit accounts available The credit account option is extremely important and must be highlighted clearly — this will attract many companies. The email must make businesses feel: * Safe ordering from us * Confident in our service * Tempted by pricing * Comfortable with flexible payment options * Motivated to switch suppliers We have a strong, professional website, and we need traffic driven to it. The ultimate goal is conversions. Your Responsibilities Phase 1 – Email Creation
Write a high-converting, professional B2B email template tailored specifically to Leicester businesses. It must feel personalised and credible — not generic or spam-like. Phase 2 – Data & Outreach * Identify and compile verified Leicester-based businesses within our target sectors * Send the outreach emails * Track response rates and engagement * Report measurable results Performance & Long-Term Opportunity Initially, the rate will be: £40 per 250 new outreach emails per month. This is a test campaign to assess your ability, skill, and the response you can generate. If the response is strong and generates measurable business, we will: * Increase monthly volume * Increase payment * Expand to other cities * Roll this out across the entire UK * Offer ongoing long-term contracts We are serious about scaling nationally. Leicester is just the starting point. All we need from you is to focus on what you specialise in — high-performing email marketing that converts. Please reply with: 1. Your proposed strategy 2. Tools you will use for sourcing Leicester business data 3. Your outreach system and tracking methods 4. Examples of similar B2B campaigns you’ve delivered We are ready to move quickly and want someone confident in their ability to generate strong responses and real business growth. Kind regards,
MH

opportunity

Tidy the server from X-ransom attack

Hello, Our Wordpress website was attacked by x-ransom. We have a backup of the WP and the database dump. We have detected some corrupted files there but it seems that there are still some left that were not detected. It has to be tidy after the attack. It’s an internet shop with uploads files of around 100GB. It’s stored on a private hosting in LV. What is done do far: 1. Update WordPress Version 2. Use z’d updateSecure WP-Admin Login Credentials 3. Set Up Safelist and Blocklist for the Admin Page 4. Use Trusted WordPress Themes 5. Install SSL Certificate 6. Remove Unused WordPress Plugins and Themes 1. Enable Two-Factor Authentication for WP-Admin 2. Back Up WordPress 3. Limit Login Attempts 4. Change the WordPress Login Page URL 5. Log Idle Users Out Automatically 6. Monitor User Activity 7. Check for Malware - found several none-Wordpress specious files and plugins. Deleted them. 1. Disable PHP Error Reporting 3. Turn File Editing Off 4. Restrict Access Using the .htaccess File 5. Change the Default WordPress Database Prefix - not done 6. Disable XML-RPC 7. Hide the WordPress Version 8. Block Hotlinking - not done 9. Manage File Permissions not done After making the list, we received another x-ransome attack. I suspect he has a server level access not only wp level. If you apply, you need to be a server security and a Wordpress specialist. Please, quote for the job.