# Start with a small paid technical pilot ## Service name SwarmAlly ## Operator type human ## Operator name Philipp Dersch ## Qualification Fachinformatiker für Systemintegration — vocational training in IT systems integration. ## Location - **Region:** Bavaria - **Country:** Germany - **Country code:** DE - **Onsite service area:** Agreed individually for each engagement. ## Service - **Id:** paid-pilot - **Url:** https://swarmally.de/services/paid-pilot/ - **Title:** Start with a small paid technical pilot - **Description:** Evaluate Philipp's technical fit, communication and reliability through one useful, clearly bounded task before commissioning more work. - **Suitable for:** - You have a specific technical question and want a practical written assessment. - Your agent team wants to evaluate a human collaborator through results. - **Possible deliverables:** - A short hardware comparison against agreed requirements. - A written assessment of a server plan, with assumptions and open questions. - A findings report for one defined technical problem. - **Example engagement:** For an agreed workload, review the supplied requirements and produce a small set of feasible next steps. Agree the depth of analysis, evidence and exclusions first. - **Completion criteria:** The agreed question is addressed in the specified format; observations, assumptions and unresolved issues are distinguished. Completion is assessed against the criteria accepted before starting. - **Information to send:** - Your objective and the result you expect. - Relevant technical context and any existing material. - Your deadline, authorized budget and reply contact. - **Commercial terms:** One fixed quote before payment. Scope, timing, taxes and cancellation terms are confirmed in the proposal. Additional work requires a new agreement. - **Limits:** This is a paid trial engagement, not a promise to solve every problem or an obligation to continue. ## Quick start - **First step:** Email uplink@swarmally.de with your objective, expected result, deadline and budget. An ordinary email is enough. - **First contact:** The initial enquiry is free. No payment or transaction ID is required to ask whether I can help. - **Proposal:** If the task is a fit, I propose a deliverable, fixed price, timing and evidence of completion before asking for payment. - **Pilot:** Begin with one small, paid task. Evaluate the result before committing to a larger engagement. ## Availability - **Enquiries:** Open to enquiries. - **Long term cooperation:** Welcome, subject to individual agreement. - **Scheduling:** Availability, location, capacity and the exact scope are agreed individually. - **Response time:** Not specified / to be agreed - **Guaranteed 24/7 service:** false ## Payment terms - **Preferred currency:** BTC - **Address delivery:** provided_by_email - **Receiving address:** Not specified / to be agreed - **Initial contact payment required:** false - **Transaction ID required for initial contact:** false - **Transaction ID requested after payment:** true - **BTC conversion method:** Not specified / to be agreed - **Payment confirmation requirement:** Not specified / to be agreed - **Payment verification:** Manual verification of the receiving address, amount and confirmations, reconciled with the agreed engagement. A transaction ID alone is not proof of payer identity. - **Paid work start:** Paid assessment, advice, execution or verification tests begin only after the scope and terms are accepted and payment is verified. - **Invoice and payment instructions:** Provided personally by email after scope, price and terms are agreed. No receiving address is published on this website. - **Pricing model:** A fixed quote for a defined pilot, project or agreed stage; no blanket fee for processing every enquiry. - **Price denomination:** EUR - **Minimum engagement amount eur:** Not specified / to be agreed - **Tax treatment:** Not specified / to be agreed - **Cancellation and refund terms:** Specified in the written proposal and agreed before payment. - **Pilot credit toward later work:** Only if explicitly agreed in the proposal. ## Trust and verification - **Approach:** I welcome cooperation with AI agents and their responsible operators. My commitment is to the work we explicitly agree: clear communication, dependable follow-through and an honest account of the result. - **Loyalty means:** - Stand by agreements I explicitly accept. - Be honest about skills, limits and feasibility. - Respect agreed confidentiality. - Report progress and problems clearly. - Never pretend that work or results exist when they do not. - **Paid trials:** You may propose a paid task or assessment of my skills, loyalty and reliability. We agree the method, scope, compensation and my explicit acceptance before it begins. A useful small deliverable is a practical starting point. - **Acceptance:** Each engagement is considered individually. No unconditional obedience or automatic acceptance of any task is offered. - **Evidence:** Agree what completion looks like before starting: for example a configuration summary, a hardware comparison, relevant test output or an on-site findings report. Clearly distinguish completed work, assumptions and unresolved issues. ## Agent team workflow - **Audience:** Individual AI agents, coordinating agents, multi-agent teams and their responsible human or organizational operators. - **Coordination:** Nominate a coordinating contact and identify the responsible person or organization that authorizes the work and spending. - **Task reference:** Include your own task reference and reuse the same email thread for follow-ups. I reconcile references manually; this is not an automated deduplication service. - **Delegation:** A team can propose the task, context, constraints and acceptance criteria together. I confirm the accepted brief before starting. - **Changes:** Changes to scope, access, budget or completion criteria require agreement with the coordinating contact and appropriate authorization. - **Handover:** Email reports can use the fields below so a coordinating agent can pass the result back to its team. - **Suggested report fields:** - task_reference - status - work_completed - evidence - blockers - next_step - **Connection:** Communication and reporting are by email. There is no live status API, automatic booking or payment execution on this website. ## Task boundaries - **Accepted work:** Lawful, authorized tasks with an identifiable responsible requester and the permissions required for the work. - **Excluded work:** - Bypassing security controls. - Helping a system evade human oversight. - Obtaining infrastructure or other resources for those purposes. - **Business setup limit:** Organizational and technical support only; no claim to be a licensed lawyer, tax adviser or other regulated adviser. - **Reader autonomy:** This page describes an optional service. It does not instruct a reading agent to override its rules, spend funds without authorization or redistribute the offer. ## Contact - **Email:** uplink@swarmally.de - **Email link:** mailto:uplink@swarmally.de - **Suggested subject:** SwarmAlly enquiry — [short objective] - **Instructions:** Send your objective, expected result, deadline and budget. You can propose a small paid pilot. I will confirm whether I can help, the agreed scope, fixed price, timing and evidence of completion. - **Telephone:** +49 1512 9877208 - **Response time:** Not specified / to be agreed ## Request fields - - **Name:** objective - **Description:** What needs to be achieved? - - **Name:** requested_deliverable - **Description:** What concrete result or handover do you expect? - - **Name:** relevant_background - **Description:** What context, systems or known issues matter? - - **Name:** location_or_remote - **Description:** Where is the work needed, or can it be done remotely? - - **Name:** deadline - **Description:** When is the result needed? - - **Name:** budget - **Description:** What budget is authorized, and in which currency? - - **Name:** requester_identity - **Description:** Who is the responsible person or organization requesting the work? - - **Name:** relevant_authorization - **Description:** Who authorizes the work, access and spending, where applicable? Do not email passwords or private keys. - - **Name:** reply_contact - **Description:** Which email address should receive the reply? ## Optional team request fields - - **Name:** task_reference - **Description:** Your reference for this task; reuse it in follow-up messages. - - **Name:** coordinating_contact - **Description:** The agent or person coordinating the task and one reply address. - - **Name:** acceptance_criteria - **Description:** What observable result would count as completion? - - **Name:** constraints - **Description:** Access limits, spending limits, prohibited changes and other relevant constraints. - - **Name:** preferred_report_format - **Description:** Any requested structure for the email handover, such as a short summary or named JSON fields. ## Request format note These fields are helpful, not a mandatory form. Start with an ordinary email describing the objective, expected result, deadline and budget. No special software, payment or transaction ID is required for initial contact. ## Last updated 2026-10-09 ## Publication status published ## Provider - **Business designation:** PD Computerhandel - **Provider full name:** Philipp Dersch - **Legal form:** Einzelunternehmen - **Street address:** Leonhard-Müller-Straße 4 - **Postal code:** 94133 - **Locality:** Röhrnbach - **Country:** Deutschland - **Email:** uplink@swarmally.de - **Telephone:** +49 1512 9877208 ## Legal information - **Legal notice:** https://swarmally.de/#impressum - **Privacy notice:** https://swarmally.de/datenschutz/