- Company sizes or stages where the product is unnecessary or insufficient
- Very early-stage startups with minimal process repetition may prefer general-purpose documentation tools (Google Docs, Notion) and manual screenshots over a dedicated capture+KMS product.
- Industries or use cases where competitors are better aligned
- If a buyer requires video-based SOPs with AI voiceovers, translation, and LMS/SCORM exports, a video-first documentation provider may be more appropriate.
- If procurement requires an extensively documented enterprise trust center and publicly documented certifications, larger KMS providers or more mature vendors may be a better fit.
- Technical requirements the product may not meet (based on public evidence)
- If a buyer requires publicly documented SOC 2 Type II / ISO 27001 certificates prior to procurement, StepHow may not meet that requirement based on the public materials reviewed.
- Budget considerations
- If the organization primarily needs many viewers and very few creators, alternative licensing models from other vendors could produce a lower TCO than a per-user creator seat model.
- Specific workflows or integration requirements
- If interactive in-app walkthroughs (tooltips, in-product guidance) are required rather than static guides, a digital adoption platform (DAP) may be more suitable.
- Red flags to watch during procurement
- Vendor-provided performance metrics and efficiency claims that do not include disclosed measurement methodology or sample details should be validated in a pilot.
- Current limitations acknowledged by the vendor or observed in public materials
- Public documentation does not include an explicit limitations page. Notable public gaps include limited third-party review coverage and lack of publicly available compliance certifications.
- Features on the roadmap (not publicly documented)
- No public, dated roadmap items were found in the accessible sources.
- Scale limitations
- No public documentation specifying scale limits or thresholds was identified.
- Security or compliance gaps
- Security certifications are not publicly documented.
- Technical debt or architecture notes (based on available public information)
- No public reports of technical debt or architecture constraints were identified in the research set.
- API and integration constraints
- A detailed public API or integration catalog was not identified in the sources reviewed; buyers should request integration documentation and connector lists during vendor evaluation.