System design resources
Free project packs, CRM rules and planning tools for AI, data and revenue systems.
Open resources
Choose what you need to inspect
Each resource answers a different implementation question. Start with the decision you need to make.
AI invoice processing
Inspect invoice arithmetic, purchase-order discrepancies and duplicate decisions using synthetic cases. The ZIP includes a CSV field dictionary, expected outputs and locally tested Python rules; it does not connect to accounting software.
Read the invoice workflow guideDownload invoice reference ZIPDocument classification and PDF splitting
Review how a split manifest keeps page ownership, document classes and repeated invoices distinct. The ZIP includes a class-policy CSV, synthetic document manifests and locally tested Python rules; it does not transform PDF files.
Read the classification and splitting guideDownload splitting reference ZIPClay Implementation Framework
Plan a reliable Clay workflow with a 16-page guide and six editable CSV worksheets for data, research, review, CRM writes and launch. Enter your email to open the downloads in your browser.
Get the implementation frameworkSample startup project deliverables
One coherent capture-to-owner specification: brief, architecture, field dictionary, six expected test cases and handover runbook.
Inspect the project packHubSpot lead routing test lab
Select six fictional inputs and inspect the proposed owner, reused contact or exception. Includes the tested local policy, acceptance matrix and runbook.
Try the routing scenariosClay and HubSpot field contract
See field ownership, permitted updates and identity checks for a bounded enrichment workflow. Includes a downloadable CSV and six expected test cases.
Read the integration rulesLead-flow planner
Change assumptions for a monthly sourcing cohort and see the calculated stages. Results come from your own assumptions.
Open the plannerUse the material
Bring the assumptions back to your own workflow
These independent AGI Technologies references use synthetic examples. Check their assumptions against your systems before a live build. For republication or redistribution, contact andrii@agitechnologies.io.
A reference document is a starting point for scoping and review.
Check the sources, identifiers, owner rules and exception path against your current tools. Use the example fixtures to specify what should happen before enabling writes or handoffs.
For startup infrastructure, we scope the capture, CRM, automation and measurement work around the operating stage. For Clay and HubSpot, the integration guide goes into more detail.
For Clay and HubSpot work, start with the account-scoring template, account-research prompt or cost-per-accepted-record worksheet. Read the examples directly in the guides and adapt the inputs to your own process; no form is required.
For a provider-by-provider cost review, use the waterfall cost measurement guide alongside the worksheet.
Implementation routes
Connect the resource to the work you need
Choose the service by the system problem, then share your current process.
Startup infrastructure
Define a phased capture, CRM and operating foundation with ownership, validation and handover.
View the scoped startup serviceClay and HubSpot implementation
Connect sourcing, reviewed research and CRM actions with explicit matching and field-write rules.
View Clay and HubSpot servicesScope the next step
Show the handoff you want to improve
Share the tools, input records, current owner rule and the result you need. We can use that context to discuss an assessment or a bounded build.