Describe the current situation
Bring the current site or tools, a short account of the problem, and the person who can approve the work. We identify the main user actions and the constraints that affect the project.
Content, existing accounts, domain ownership, integrations, and internal permissions can change the scope. We surface those dependencies before promising an implementation.
Review a working direction
A prototype can be a page, a small interaction, or a simulated workflow. It gives people something specific to review before the full build. Its limits should be visible: a design study is not the same as a connected production system.
Agree on the first scope and the review points. Features outside that scope go into a later decision instead of becoming an implied commitment.
Build around the actual workflow
We implement the agreed screens and connections, then check the important paths. For a contact form, that includes validation, confirmation, and a fallback contact method. For a private portal, it also includes who may read and change a record.
Explore the service scopesPlan the handoff
Before launch, identify the account owners, update process, and person responsible for failed integrations or access requests. Documentation and ongoing support are part of the scope discussion, not assumptions.
Tell us what you need
Share the current site or process, the people using it, and what needs to change. We will review that context before recommending a scope.
