Update Pages Pricing info on website

[sknep]

We need to communicate updated pricing info for the Pages cost block on cloud.gov/pricing, specifically:

• Instead of $35,000, this offering costs one entire Femto tier, which is $30,000 / 600 credits
• Can be bundled with other Cloud.gov offerings at higher tiers
• Includes 4 production websites, not 5
• Additional production domains are available for 144 credits annually, each (not in packs of 3)

@eschneid3 if you're assigned this by @hursey013, could you come up with a draft of the changes (figma, screenshot, live branch build, whatever fits) and then run it by me and @anjunainaustin (Eleni) for review? It might take a small amount of reformatting that box, since the big price text now needs to say something like "600 Credits"

[eschneid3]

Updated Pages pricing section design:

[pburkholder]

Thanks Emelia - the more I work on our credit pricing the more I think of the Washington's Dream skit from SNL.

How many Pages sites can fit in a Femto? Nobody knows!

Anyhow I think should read: Pages at 144 credits/year per site, can be combined with other services, and there's a 600 credit minimum for any bundle.

Would you like me to mark up your mockup?

[eschneid3]

Here is an update based on your and Sarah's feedback. Let me know your thoughts. Follow up question: Do we typically talk about prices on an annual basis with customers? I noticed that the Workshop credits listed on the pricing page are per month.

[svenaas]

I believe credits for Pages sites are used per domain, not per site. Tagging @apburnes and @zjrgov to be sure.

(I realize this is a nuanced distinction depending on the audience, but sites and domains are distinct things in Pages and the difference has caused confusion with a customer as recently as this month.)

[zjrgov]

TLDR: use site; by looking at the table screenshot I think it's clear why domain would be more confusing than site to the typical customer.

IMO site is the clearer possible nomenclature. I'll attach the example table from the memo, but it's essentially a difference of "do domain X and domain Y go to the same place? If so, same site charge,".

The most likely edge case to me would be:

Address	Location
agency.gov	Website A
agency-foo.gov	Website A

In such a scenario, is agency-foo.gov a redirect that Agency manages? If so, doesn't seem like we'd bill for it. But if Agency is asking us to manage DNS for agency-foo.gov for them, to me that seems grayish — perhaps intersecting with the lack of a static IP offering on our end — and may not have an explicit policy.

[svenaas]

@zjrgov The terms "site" and "domain" are presented in the Pages interface as specific things. Recently we worked with a customer who found themselves on a higher tier under the new pricing. They knew they had some old things they could clean up, but initially they did work with @apburnes removing sites because they thought removing sites was what would lower their quote. But this work did not have the effect they wanted, because what they really needed to do was deprovision domains.

[svenaas]

@eschneid3 Currently https://cloud.gov/pricing/ shows credits/year as the primary reference, with credits/month underneath for convenience (see below). Could we do that for Pages as well?

and

[zjrgov]

@svenaas that does sound confusing! Is that actually how the pricing should work, though, under credits?

• In the pages UI, does a redirecting subdomain count as a capital "D" Domain, or is that something else?
• which thing costs us the most? or is it about the same?

[svenaas]

@zjrgov I don't know the answer to either of those bulleted questions. Tagging @apburnes.

I can say though that sites in Pages could be considered part of dev / staging. Customers can spin up various sites as they try things out without worrying about incremental costs. It's only when the site gets provisioned with a domain that it becomes accessible through the CDN at a predictable and presentable URL, which is the service we charge for (note that domains like beta.ouragency.gov or staging.ouragency.gov are production domains as far as Pages is concerned and count as such regardless of how they are used).

So a customer might have half a dozen sites but only two domains. It's the domains that should consume credits.

[apburnes]

A site has many custom domains. Any custom domain we provision for a site is added to their total custom domain count. We don't support redirecting subdomains from pages. The infrastructure to support demo.agency.gov or agency.gov is the same.

[pburkholder]

Is there a PR to review for this? It seems like we've got all the questions answered.

[eschneid3]

Here is an updated mock based on the above discussion. Let me know your thoughts on whether this more accurately represents the pricing model.

[svenaas]

Thanks, @eschneid3. Eleni confirmed this in Slack and I concur that we should go ahead based on this mock.