Guide contents
What you getA published page, a form and a place to review submissions.

A page with a form brings several roles together: marketing shapes the offer, design sets the look, sales receives the lead. With Octo Cloud you can ask the agent to build and host such a service. We start with a practice page so you can check the whole path on test data.

01

What to prepare

  • Make sure Octo Cloud is available in your workspace. Ask Octodus to confirm the hosting terms before you start.
  • Prepare the offer, the copy and the form fields. For the exercise, download the brief for a portfolio review signup page.
  • Use test contacts. Decide who should see incoming submissions and where you prefer to review them.

The source files use sample data. Replace it with your own once you know the process.

02

Describe the whole result

Ask for the page, a working form, data storage and a way to view the data. If you only say "build a landing page", you can easily get a design without a finished lead-collection flow.

Ask the agent to name the access it needs and the hosting terms. One simple scenario is enough for the practice project; you can add more integrations after the basics work.

Task for Octodus
Using the attached brief, build a practice page with a form in Octo Cloud. I need submissions saved and a way for me to view them. Use test data. First confirm the hosting terms and the access you need, then show me a plan. Once it is built, give me the link and explain where to find a submitted lead.

03

Walk the visitor's path

Open the link you were given and check the page on your phone. Submit a test lead and find it in the storage place Octodus showed you.

Check empty required fields and an invalid contact. After a successful submit, the person should understand what happened and what to expect next.

Task for Octodus
Check the whole form flow: a valid submission is saved, empty required fields and an invalid email are rejected, and a second click while sending does not create a duplicate. Make sure the list of submissions is not accessible to a regular visitor. Show me the results and say what you could not verify.

04

Example result

Practice example · Reference for your check

Example test lead

  • Name: Test Attendee. Email: [email protected]. Goal: check that the lead is saved.
  • After submitting, find the record with the same values. Refresh the submissions view and confirm the record is still there.
  • Then change the page title and test the form again: a visual edit must not break saving.
05

The key catch and the check

A form on the screen and a saved lead are two different results. Check them separately. Before you collect real leads, set up the terms for handling personal data and your team's access to the records.

Before you use the result

  • The link opens, and the page and form work well on a phone.
  • A successful submit creates a record with the right fields.
  • Input errors are clear, and data is not lost without explanation.
  • The submissions view is available to the right people, not to every visitor.
06

How to repeat this on your own task

Next you can change the copy, add fields or connect a lead to a workflow. In every task, say that records already saved must be kept. If you want to understand the service and its database in more depth, continue with the Postgres lesson.

Try this scenario

Download the source file, copy the task and send it to Octodus together with the file.

Next stepDeploy a service with Postgres and update it