A four-week plan for getting an application ready

Businesses do not fail to prepare an application because the work is hard. They fail because it is treated as a document to be produced rather than as a project with a critical path, and the two items with the longest lead times are the two that get started last.

Here is the plan that does not do that. Four weeks is realistic for most single-domain businesses and optimistic for a multi-domain brand in a compounded category, which is a reason to start earlier rather than to compress it.

Before week one: name the owner

One person, with the authority to get a website change deployed and the calendar space to answer correspondence within a day for the duration of a review. If that person does not exist, everything below will slip, and it will slip invisibly.

Write down who it is. This is the single strongest predictor of how the review goes, which is the argument the rework loop makes at length.

Week one: the two things with lead times

Pull the domain list from the registrar, the DNS provider and the hosting account, and record a decision against each domain: certify, redirect, retire. Everything downstream is scoped by this, and a business that audits one website and then discovers three more has audited the wrong amount.

Ask your pharmacy partner for its documentation on day one. The legal entity that dispenses, the registration type and numbers, the states it is licensed to ship into, the scope of what it prepares for you, and the agreement. This depends on somebody else's priorities, which is exactly why it cannot wait.

Then start the website audit in the same week, because it is the longest piece of work and every day it does not start is a day added to the end.

Week two: the claims audit and the allowlist

Read every page a patient can reach. Not the sitemap: landing page variants still receiving traffic, quiz result screens, the shop, email sequences, support macros and affiliate creative.

Test every product claim against one question: could you evidence this to somebody who is not inclined to believe you?

The output is two documents. A fix list, with an owner and a date against each item. And a claims allowlist per product, saying what the preparation is, what may be said about it, what may not, and the exact approved phrasing for the two or three things everybody wants to say.

The allowlist is the one that outlives the application, because it is what stops the next landing page reintroducing the problem.

Week two, in parallel: the collection work

None of this is difficult and all of it takes longer than planned, which is why it runs alongside rather than after.

• Entity documents, ownership and the principals, including any prior regulatory history.
• The provider roster with licences and states, and the medical director.
• The state coverage matrix: states marketed in, states prescribers are licensed in, states the pharmacy may ship into.
• Processing history if you have it, including dispute and refund rates.
• The subscription mechanics as a customer experiences them.

Week three: fix and reconcile

The fix list goes into a sprint rather than into a favour, which is a negotiation worth handling deliberately.

Meanwhile, reconcile the four accounts of your business: what the application will say, what the website says, what the public record says, and what your partners say. Read them side by side and look for the sentence where two of them describe the business differently. Most avoidable requests for information are generated by exactly that.

Week four: read it as a stranger, then file

Two tests before submission.

The stranger test. Could somebody who has never seen your business, reading only your submission and your website, describe accurately what you sell, who prescribes it, who makes it and what it is not?

The outstanding-items test. Is anything on the fix list still open? Filing over an open fix list is filing for the request for information you already know is coming.

Then file, once, for every domain that needs it. The complete file is what you are submitting rather than a form with attachments to follow.

What slips, and what to do about it

The pharmacy documentation. Chase weekly from day one and escalate to the commercial relationship rather than the compliance inbox if it stalls.

The engineering time. Size the fix list in week two so it can be scheduled rather than discovered.

The person who knows the corporate history. Founders travel. Get the ownership and prior-history questions answered in week one while somebody is in the room.

The scope. A domain discovered in week three re-opens the audit. This is why week one is the registrar rather than the website.

Where a shorter timeline is honestly possible

Some businesses can compress this and it is worth saying which, because the four weeks above is a plan rather than a floor.

A single domain with a small catalogue of approved products prescribed generically, no compounded preparations, an existing licence roster and a founder who can answer questions the same day is genuinely a two-week exercise. The audit is small because the site says less, and the eligibility questions are settled before they are asked.

What cannot be compressed is anything depending on somebody else. Pharmacy documentation, corporate records held by a departed founder, licensure evidence from a credentialing partner and engineering time all move at their own pace, and no amount of preparation urgency changes that.

So the honest reading of a compressed plan is that it works when the critical path runs entirely inside your own building. The moment it leaves, the schedule belongs to whoever is at the other end of it.

The part that is genuinely fixed

None of this shortens the review. The review begins on submission and runs as long as the questions take, and what LegitScript will and will not commit to is worth reading before promising anybody a date.

What the plan changes is the number of questions the file generates, and that is the half of the timeline that belongs to you.