A legacy Webflow build for AutoEntry, held as a proof card pending recovered details
A product story that needed more than a brochure layout
The project called for a Webflow experience that could carry a more technical product story — one involving integrations and interactive behavior — without becoming difficult for the client to maintain afterward.
Support the build without over-committing to unverified detail
SoFlow delivered Webflow implementation support built around custom interactions and integration-oriented structure. Because the original documentation for this engagement is incomplete, the exact public-safe detail should be confirmed with the client before this is expanded into a full case study.
A holding entry for real integration and interaction work
Until the original brief and visuals are recovered, this entry should stay a short, honest proof card rather than a stretched-out narrative.
Our other projects
The brief was to support a Webflow project for AutoEntry, Sage's accounts-payable automation product, where integration behavior and interactive presentation mattered more than a static brochure layout.
The project needed a controlled Webflow experience that could support a more technical product story without becoming difficult to maintain going forward.
The original implementation details for this engagement are not fully documented in the current record, so this entry should remain a short, transparent proof card until source material — brief, screenshots, and scope notes — is recovered.
SoFlow delivered Webflow implementation support centered on custom interaction and integration-oriented work for AutoEntry by Sage. The exact public-safe detail should be confirmed with the client before this is published as a full case study.
Webflow served as the public presentation layer, while custom implementation work handled the more technical, integration-oriented parts of the experience. Further architecture detail is not available in the current record.
- Webflow implementation support for a product-led experience
- Interaction-led presentation beyond static content
- Integration-oriented project structure
This entry should be treated as a short proof card rather than a complete case study until the original implementation detail is recovered.
- Existing, verified Work item in the SoFlow CMS
- Services tagged to integration, interaction design, and Webflow development
Is this a complete, publishable case study?
Not yet, and it shouldn't be treated as one. This entry predates SoFlow's current documentation process, so the original brief, screenshots, and implementation notes are incomplete. It's kept in the Work library as a proof point of integration and interaction capability, not as a finished narrative — flag it for a rewrite once source material is recovered or the client confirms public-safe detail.
Did SoFlow build AutoEntry?
No. AutoEntry is Sage's own accounting automation product. SoFlow's role was Webflow implementation — supporting a more technical product story with custom interactions and integration-oriented structure, not building or owning the AutoEntry software itself.
Should private implementation details be published here?
No. Until the original scope is confirmed, the public page should stick to the general business problem and visible outcome, without exposing specific integration mechanics, credentials, or client-confidential detail.
This entry shows SoFlow takes on Webflow projects that require more than page layout and basic CMS setup — including integration-oriented, interaction-led product experiences like AutoEntry's.
Is this a complete, publishable case study?
Not yet, and it shouldn't be treated as one. This entry predates SoFlow's current documentation process, so the original brief, screenshots, and implementation notes are incomplete. It's kept in the Work library as a proof point of integration and interaction capability, not as a finished narrative — flag it for a rewrite once source material is recovered or the client confirms public-safe detail.
Did SoFlow build AutoEntry?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Detailed before-state context for this engagement hasn't been recovered yet, so it isn't published here until source material is available.
The project stands as a Webflow Work proof point for SoFlow's integration and interaction capability, pending fuller documentation.
This entry should stay positioned around Webflow plus integration and interaction support specifically, not framed as a generic visual website build, since that's the part of the work that's actually distinct.
