Product visual
founded
ATZ CRM
Recruitment · B2B SaaS experience covering AI, Web app, Workflow automation, CRM integrations.
- Recruitment
- B2B SaaS
Case studies by technology
Web application experience across five different operating models.
Shared web-application experience does not imply that every story used the same framework, architecture, scale, or engagement model.
Exact relationship
Relevant workflow
Source boundary
Evidence-led archive
Inspectable stories
Buyer questions
Related services
Relevant stories
5 attributable stories in the current catalog.
Shared web-application experience does not imply that every story used the same framework, architecture, scale, or engagement model.
Product visual
founded
Fieldified
Field services · B2B SaaS experience covering Web app, Mobile workflows, Payments, Automation.
- Field services
- B2B SaaS
Product visual
founded
LendControl
Rental operations · B2B SaaS experience covering Web app, Inventory, Payments, Automation.
- Rental operations
- B2B SaaS
Product visual
founding engineer
CuFront Healthcare
Healthcare · Healthtech SaaS experience covering Web app, Healthcare workflows, AI, Operational reporting.
- Healthcare
- Healthtech SaaS
Product visual
college startup
Externship
Education · Marketplace experience covering Web platform, Partner operations, Marketplace workflows.
- Education
- Marketplace
| Story | Relationship | Industry context | Technology context |
|---|---|---|---|
| ATZ CRM | founded | Recruitment, B2B SaaS | AI, Web app, Workflow automation, CRM integrations |
| Fieldified | founded | Field services, B2B SaaS | Web app, Mobile workflows, Payments, Automation |
| LendControl | founded | Rental operations, B2B SaaS | Web app, Inventory, Payments, Automation |
| CuFront Healthcare | founding engineer | Healthcare, Healthtech SaaS | Web app, Healthcare workflows, AI, Operational reporting |
| Externship | college startup | Education, Marketplace | Web platform, Partner operations, Marketplace workflows |
Context
Why this category changes product and engineering decisions.
These sections make the archive useful even when the attributable proof set is intentionally small.
Transactional SaaS
Recruitment and rental products need durable records, permissions, workflow state, documents, integrations, and reporting.
Physical operations
Field and rental systems connect web state to technicians, assets, locations, evidence, and money.
High-trust domains
Healthcare and education marketplaces require deliberate identity, responsibility, privacy, and evidence boundaries.
Buyer evaluation
Questions to ask before treating a logo as proof.
Strong evidence connects the named relationship to technical scope, decisions, outcomes, sources, and the period in which the work occurred.
What is the source of truth?
Identify records, ownership, identifiers, history, correction, and reconciliation.
Which workflows are transactional?
Protect commitments, money, inventory, documents, and irreversible actions.
How are users separated?
Review tenant, organization, role, purpose, privileged access, and external portals.
How will another team operate it?
Inspect tests, deployment, observability, documentation, support, and handover.
Questions, answered
Web application experience across five different operating models. questions, answered
Relationship, evidence, technology attribution, and outcome boundaries in plain language.
Are all five stories Automiq client projects?
No. Three are products founded by Ayush Sharma, one is founding-engineer experience, and one is a college startup. Each page states the relationship.
Do all cases disclose their complete technology stack?
No. Technology links may show relevant engineering decisions, while private implementation details are only attributed when a source or approval exists.
Talk to the engineering team
Ask us how this experience applies to your product.
We will separate directly relevant lessons from assumptions and define the evidence needed for your first production milestone.