DanubiSoft: client-ready next steps

Search available meeting records for newer DanubiSoft meetings, then read the two newest full transcripts, including continuations. Reconcile every relevant promised effort with an artifact, owner and next action.

Verification: Record discovery coverage, transcript identity/date, full-read coverage and supporting passages. Existing September 10/16 copies are starting points, not proof they remain newest.

Refresh material campaign status and numbers, and keep emails, replies, positive interest and held consultations distinct.

Verification: Record retrieval time, source and arithmetic; label client-side outcomes unknown unless independently evidenced.

Keep the unrelated Molnár attachment and hypothetical foreign fee examples out of DanubiSoft commercial claims.

Verification: Compare all commercial claims with the April agreement and meeting ledger.

Define source systems, unique-contact/company rules, response and positive-response views, full-thread link/retention fields, exclusions, priority, owner, timing and QA before any send. Include a short operator handoff with exact export/query inputs, segment-to-draft mapping, queue fields, suppression refresh and launch-readiness checks.

Verification: Document retrievable campaign/list identifiers and field mappings; check at least five real source records covering human replies, a positive reply if one exists, timing/negative replies and a no-reply contact if available. For no-reply records verify sent history and absence of inbound reply rather than inventing a thread. Explain unavailable categories.

Provide a small prioritized real-contact sample with rationale and at least three short, segment-specific Hungarian draft patterns; distinguish 'we emailed' from 'we spoke'.

Verification: Cross-check every personal detail and date against source threads; mark unknown context rather than inventing it.

Exclude unsubscribes, hard negatives, client exclusions and already-active conversations from proposed recontact.

Verification: Document the actual exclusion check for each sampled candidate and the rule for the full later queue.

Make reactivation executable from existing systems without a prerequisite CRM rebuild: name actual campaign/list sources, exact retrieval route and fields, deduplication key, respondent/positive filters, missing data handling, queue production steps and next owner. Retain available full thread evidence for the sample in private local/provider sources.

Verification: Walk one sampled contact through retrieval, deduplication, segment, exclusions, draft and proposed queue row. A narrative strategy alone does not pass. If full export is unavailable, prove a read-only route on the sample and explicitly identify remaining full-queue retrieval work.

Preflight actual Instantly Email API access and history coverage; lead CSV alone does not supply reply bodies. Use paginated all-message retrieval, retain thread IDs and check Others/unmatched replies. Reconcile sampled priority threads against connected mailbox or another retained complete source where available.

Verification: Record actual access, pagination and coverage results. Follow current endpoint limits. Distinguish unavailable archive coverage from no reply; do not certify a complete historic inventory from Unibox alone. If access fails, try retained full-thread evidence or authenticated mailbox readback and disclose the precise remaining gap.

Deliver one concise Hungarian email draft and one-page, presentable brief with exact dated metrics, a useful soft-negative example and explicit unknown outcomes.

Verification: Compare figures and examples with the ledger; verify the final brief renders and all review links work. Verify email-mihaly.md is Hungarian, unsent, sourced, concise and ends with one clear client request.

Specify 2–3 bounded experiments for existing-list enrichment, a new domestic source and new offer/message angle, each with sample size, ICP, success signal and stop/iterate rule.

Verification: Verify source availability and distinguish proposed tests from proven acquisition or client-approved offer.

Give European POEM APS partner outreach a separate first-wave plan with partner criteria, contact verification, value proposition and decisions needed on product readiness and terms. Specify proposed first-wave sample size, owner/timing, success signal and stop/iterate rule. Make launch conditional on actual landing/product readiness and settled offer/terms, not an assumed calendar date.

Verification: Check against meeting commitments and existing partner materials; keep raw company counts and hypothetical fees qualified. State product/ERP-version claims needing DanubiSoft confirmation. Preserve no partner-size minimum unless newer client evidence changes it.

Do not send client messages, launch campaigns, alter provider data or make binding price/fee commitments.

Verification: Report draft and provider states separately in the handoff.

Publish the client-facing HTML through comment-html-review-host at a stable bare URL, retaining document identity. INDEX.md must link every final deliverable, with local absolute links for internal source evidence. Do not publish raw transcripts, contact details or full threads.

Verification: Read back the hosted page and its review identity, check final links, and compare unrelated host routes before/after publication. Verify actual rendering without opening a user-facing panel. Apply the required Luna section screenshot loop if the output becomes a client-facing website; simple document HTML is exempt.