← Ethos
First-time day at Ethos

Speed up package select while the payment disclosure stays visible

You’re the software engineer. Your team is in the room. Printed Oct 13, 2026.

The payment disclosure protects informed purchase, while its rendering delays package selection on mobile.

Applicants need a fast final choice, and the carrier disclosure must remain visible before checkout.

Who you’d be doing this for

“I got approved, then the package page just sat there while my lunch break ended.”

Martin Lazarevic · Approved life insurance applicant

She completed the application on her phone and is trying to select a policy package before returning to work.

What is at stake

Mobile package-select completion fell to 54% after the disclosure release, while desktop performance held steady. You have to weigh faster rendering against proof that every shopper still sees the required disclosure.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • mobile speed vs disclosure visibility
  • conversion recovery vs package comparison context
  • rapid release vs regression confidence

Why Ethos

The direct application journey turns approved shoppers into activated policies through a mobile package-select and checkout flow.

Written with these in mind

performance-minded fullstack buildercustomer-journey engineerquality-focused product engineer

Not your kind of problem? 29 more at Ethos, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.