<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.vmware.com/docs/platform-as-a-product-wp"/>
	<rdf:li rdf:resource="https://netapinotes.com/api-product-strategy-more-than-just-a-feature-roadmap/"/>
	<rdf:li rdf:resource="https://tante.cc/2024/09/03/why-ai-projects-fail/"/>
	<rdf:li rdf:resource="https://archive.ph/2024.08.27-234709/https://www.linkedin.com/posts/danklyn_cows-that-agriculture-wont-allow-john-activity-7120862030776991745-zWPt"/>
	<rdf:li rdf:resource="https://www.linkedin.com/posts/danklyn_ugcPost-7234212266022203392-Vpr6/"/>
	<rdf:li rdf:resource="https://tomgeraghty.co.uk/index.php/platform-as-a-product/"/>
	<rdf:li rdf:resource="https://netapinotes.substack.com/p/is-api-product-management-a-role"/>
	<rdf:li rdf:resource="https://www.lastweekinaws.com/blog/Why-AWS-Might-Be-the-Next-Backbone-Provider/?ck_subscriber_id=512832446"/>
	<rdf:li rdf:resource="https://www.glean.com/"/>
	<rdf:li rdf:resource="https://www.linkedin.com/pulse/two-breeds-api-products-solutions-amancio-bouza-phd/"/>
	<rdf:li rdf:resource="https://www.june.so/great-product/tango"/>
	<rdf:li rdf:resource="https://medium.com/the-pattern/building-api-growth-strategies-632a8bcb0f9c"/>
	<rdf:li rdf:resource="https://anuragwadehra.substack.com/p/pursuing-business-growth-with-apis?s=r"/>
	<rdf:li rdf:resource="https://nordicapis.com/8-unexpected-challenges-of-running-an-api-as-a-product/"/>
	<rdf:li rdf:resource="https://gist.github.com/ramalho/93b87e961b6e019be8e1f6f82864b6f9"/>
	<rdf:li rdf:resource="https://www.slideshare.net/launchany/apistrat-keynote-lessons-in-transforming-the-enterprise-to-an-api-platform"/>
	<rdf:li rdf:resource="https://matthewreinbold.com/2018/07/10/Update-on-NPS"/>
	<rdf:li rdf:resource="https://matthewreinbold.com/2018/03/12/ProductManagementInAPIDesign/"/>
	<rdf:li rdf:resource="https://medium.com/capital-one-developers/api-product-ownership-is-key-for-api-adoption-6a12c64b2c83"/>
	<rdf:li rdf:resource="https://glutenproject.com/certified-gluten-free-jolly-ranchers"/>
	<rdf:li rdf:resource="https://blog.keen.io/platforms-vs-products-8994f4d726c7"/>
	<rdf:li rdf:resource="http://busse.io/who-should-write-the-sample-apps-for-an-enterprise-api-product/"/>
	<rdf:li rdf:resource="https://stratechery.com/2016/how-google-cloud-platform-is-challenging-aws/"/>
	<rdf:li rdf:resource="https://medium.com/@juliamitelman/the-product-manager-vs-the-strategist-49049a8e079f"/>
	<rdf:li rdf:resource="https://community.apigee.com/articles/2514/how-to-restrict-api-resources-by-their-full-path-a.html"/>
	<rdf:li rdf:resource="http://mcfunley.com/data-driven-products-now"/>
	<rdf:li rdf:resource="http://blog.statuspage.io/user-experience-means-more-than-a-good-product"/>
	<rdf:li rdf:resource="http://blog.programmableweb.com/2013/04/16/every-cloud-service-needs-an-api-product-manager/"/>
	<rdf:li rdf:resource="http://news.ycombinator.com/item?id=3554206"/>
	<rdf:li rdf:resource="http://kylelacy.com/stop-talking-about-products-and-services/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.vmware.com/docs/platform-as-a-product-wp">
    <title>Why You Should Treat Your Platform as a Product</title>
    <dc:date>2026-06-19T21:38:18+00:00</dc:date>
    <link>https://www.vmware.com/docs/platform-as-a-product-wp</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Cote adapted latest version]]></description>
<dc:subject>platforms products whitepaper</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:15dcf6b90508/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:whitepaper"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://netapinotes.com/api-product-strategy-more-than-just-a-feature-roadmap/">
    <title>API Product Strategy: More Than Just a Feature Roadmap</title>
    <dc:date>2025-12-16T23:57:36+00:00</dc:date>
    <link>https://netapinotes.com/api-product-strategy-more-than-just-a-feature-roadmap/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Listen, I get it: 9 out of every 10 API improvement efforts are launched in the belly of a company's engineering organization. The framing used to describe these efforts, and the APIs they produce, are natural extensions of the disciplines from which they are derived. However, shifting an organization from "API as a feature set" to "API as a strategic business driver" requires process AND language change. API product owners and change leaders must be intentional about:

Framing APIs in terms of business value, not just technical capability.
Shaping API roadmaps to align with business initiatives, not punch lists of programmatic geegaws.
Embedding API ownership, measurement, and accountability across teams.
Those things are easier said than done. But they are the difference between scattershot, unaligned efforts that are eventually abandoned when the next tech trend comes along, and ongoing API investment that drives the business forward.</blockquote>]]></description>
<dc:subject>apis products strategy</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:61258b204689/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:strategy"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tante.cc/2024/09/03/why-ai-projects-fail/">
    <title>Why &quot;AI&quot; projects fail</title>
    <dc:date>2024-09-04T21:32:14+00:00</dc:date>
    <link>https://tante.cc/2024/09/03/why-ai-projects-fail/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>we’ve been doing this for decades now, with every new technology we spend a lot of money to get a lot of bloody noses for way too little outcome. Because we keep not looking at actual, real problems in front of us – that the people affected by them probably can tell you at least a significant part of the solution to. No we want a magic tool to make the problem disappear. Which is a significantly different thing than solving it.</blockquote>]]></description>
<dc:subject>ai technology products programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:3004b84540ed/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://archive.ph/2024.08.27-234709/https://www.linkedin.com/posts/danklyn_cows-that-agriculture-wont-allow-john-activity-7120862030776991745-zWPt">
    <title>Dan Klyn on LinkedIn: &quot;Cows that agriculture won't allow&quot; - John Cale https://lnkd.in/gTR4J4fh</title>
    <dc:date>2024-08-27T23:52:03+00:00</dc:date>
    <link>https://archive.ph/2024.08.27-234709/https://www.linkedin.com/posts/danklyn_cows-that-agriculture-wont-allow-john-activity-7120862030776991745-zWPt</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Note card drawn by Jeff Patton of a cow with dashed lines to indicate the domains of the different software teams: the flank steak team, the sirloin team, the rump roast team..  

His point was that somehow these teams are expected to produce whole cows.

The notecard is signed by JP, who drew it for me over breakfast in Salt Lake City a few years ago
</blockquote>
later: "We all work on the flank steak team, and want to build Bessie. What the market seems to want from us is livestock."]]></description>
<dc:subject>drawing products productmanagement cows</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f86cfef0c693/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:drawing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cows"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/posts/danklyn_ugcPost-7234212266022203392-Vpr6/">
    <title>(28) Post | LinkedIn</title>
    <dc:date>2024-08-27T22:55:58+00:00</dc:date>
    <link>https://www.linkedin.com/posts/danklyn_ugcPost-7234212266022203392-Vpr6/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Slides are great, but the whole product drawing is particularly good
<blockquote> the ladder of extraction (from last week) hits especially hard when paired with Mr. Patton's notecard drawing. We all work on the flank steak team, and want to build Bessie. What the market seems to want from us is livestock..</blockquote>]]></description>
<dc:subject>systems complexity slides products productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:903c613fee06/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:complexity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tomgeraghty.co.uk/index.php/platform-as-a-product/">
    <title>Platform as a Product | Tom Geraghty</title>
    <dc:date>2024-04-04T22:24:34+00:00</dc:date>
    <link>https://tomgeraghty.co.uk/index.php/platform-as-a-product/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Via Abby
<blockquote>It has users / customers, who are the key stakeholders in how the product should deliver value.
It’s long-lived.
It evolves over time in response to the needs and desires of the customers.
It’s “owned” by a person or team.
It only does what it needs to do. It as important to remove unused or under-used features as much as it is to evolve new features and functions.
It has a name.</blockquote>]]></description>
<dc:subject>platformengineering products productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:081967877a2e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platformengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://netapinotes.substack.com/p/is-api-product-management-a-role">
    <title>Is API Product Management a Role or a Person?</title>
    <dc:date>2024-01-10T04:09:43+00:00</dc:date>
    <link>https://netapinotes.substack.com/p/is-api-product-management-a-role</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Which is easier? Teaching an engineer product management? Or educating a product manager about technical concerns? 
Hopefully, I've established that APIs that are treated only as a "technical" concern create risk. At a minimum, they exhibit weak product characteristics that will age poorly over time. Someone involved with API creation needs to perform the API product management role. But this discussion raises an interesting question: is it easier to train someone on the software developer team to execute the API product management role? Or does it make more sense to educate a software product manager on the technical aspects related to APIs? 

The answer is contextual for your organization. A vast degree of how that question is answered depends on the available talent. Some engineers naturally gravitate towards product-centric thinking, while certain product managers might have a knack for technical details.</blockquote>]]></description>
<dc:subject>apis products</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:216259834926/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.lastweekinaws.com/blog/Why-AWS-Might-Be-the-Next-Backbone-Provider/?ck_subscriber_id=512832446">
    <title>Why AWS Might Be the Next Backbone Provider - Last Week in AWS Blog</title>
    <dc:date>2023-04-28T18:25:57+00:00</dc:date>
    <link>https://www.lastweekinaws.com/blog/Why-AWS-Might-Be-the-Next-Backbone-Provider/?ck_subscriber_id=512832446</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>It would be grand if AWS could create higher-up-the-stack products that deliver business value. The problem is that Amazon has spent nearly three decades being very, very bad at designing anything that even remotely looks like an appealing user interface. The front page of the retail web store isn’t a good site, it’s just that we as customers have grown used to navigating its non-ergonomic design. (Credit where it’s due: Amazon nailed the user interface for Kindle Oasis. Push the button, the page turns, and it gets out of your way.) Similarly, a building’s plumbing doesn’t have to be visually appealing or user-approachable, it just has to work.

But higher-order offerings that unlock greater business value — and their corresponding margins for vendors — absolutely need to get the customer experience correct. This is something that Microsoft understands in a way that AWS does not. Unless Amazon changes its trajectory, the future I see is that AWS goes the way of the Tier 1 backbone providers — effectively, a series of underlying infrastructure that powers the things that deliver customer value.

Folks who build on AWS now will either pivot to platforms that generate bigger business value or find themselves working in the province of plumbers</blockquote>]]></description>
<dc:subject>aws ec2 business value products</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ff71ac5e7164/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ec2"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:value"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.glean.com/">
    <title>Home</title>
    <dc:date>2023-02-09T00:49:47+00:00</dc:date>
    <link>https://www.glean.com/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Moma for everyone?]]></description>
<dc:subject>startups enterprise search knowledge products</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:241756c528c5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:startups"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:enterprise"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:knowledge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linkedin.com/pulse/two-breeds-api-products-solutions-amancio-bouza-phd/">
    <title>(57) Two Breeds of API: API Products and API Solutions | LinkedIn</title>
    <dc:date>2022-12-01T01:45:35+00:00</dc:date>
    <link>https://www.linkedin.com/pulse/two-breeds-api-products-solutions-amancio-bouza-phd/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[tries to make a distinction btw solution and product, but I disagree.
still, an interesting read.]]></description>
<dc:subject>apis products</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:aa3351416bdb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.june.so/great-product/tango">
    <title>Great Products - Tango</title>
    <dc:date>2022-09-07T21:55:52+00:00</dc:date>
    <link>https://www.june.so/great-product/tango</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Tango is a browser extension that generates beautiful step-by-step guides while you work. Like really beautiful.

The product was launched last year and rapidly spread over the internet. According to the Chrome store the extension has more than 100k users now.

For some reason the product reminds me of Clockwise. A Chrome extension dead simple to understand or use. And highly valuable from the first usage.

To give some context, I’d say two recent trends speed up the path to success of Tango.

1. Remote: Tango was born during the emerge of remote which makes sense. It lets teams document things async and share.

2. Product-Led: Tango is the definition of “show, don”t tell”. It lets companies show how their product works to their customers, in seconds.

</blockquote>]]></description>
<dc:subject>tools documentation guides tutorials products teaching</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a72551114212/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:guides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tutorials"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:teaching"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/the-pattern/building-api-growth-strategies-632a8bcb0f9c">
    <title>Building API growth strategies. Exploring a few principles on building… | by Minh Nguyen | Pattern | Medium</title>
    <dc:date>2022-03-23T19:17:39+00:00</dc:date>
    <link>https://medium.com/the-pattern/building-api-growth-strategies-632a8bcb0f9c</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["In this ‘unbundled’ technology ecosystem, APIs are the fabric that connects all these fragmented yet inter-dependent parts. It is the technology layer that allows information to travel seamlessly and transactions to operate securely. As a consequence, a variety of products and business models have emerged:
products with API-first distribution eg. Twilio, Stripe, Onfido
products connecting APIs together eg. Tray.io, Segment, TrueLayer, Plaid, Fidel API
products aimed at developers eg. Snyk, Gitlab, Sentry, Pusher
product complemented by API features eg. Intercom, Airtable, Typeform
products with two-sided markets eg. Twitter API, Facebook
products with API as a secondary partner channel eg. Skyscanner
products with openness driven by regulations: open banking PSD2
…
Each of these types of product have their revenue model, this article will focus on API-first products, and how they present unfair advantages (1), enable platform strategies (2), and power defensible growth (3)."

In this context, we don’t mean platforms as marketplaces (eg. eBay, Amazon, Airbnb), where the value is created by the presence of other users (cf. one-sided or two-sided markets).]]></description>
<dc:subject>apis products productmanagement growth marketplaces</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:465ffb8a2128/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:growth"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:marketplaces"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://anuragwadehra.substack.com/p/pursuing-business-growth-with-apis?s=r">
    <title>Pursuing Business Growth with APIs - by Anurag Wadehra</title>
    <dc:date>2022-03-23T19:14:15+00:00</dc:date>
    <link>https://anuragwadehra.substack.com/p/pursuing-business-growth-with-apis?s=r</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Nice interview with Bala]]></description>
<dc:subject>apis products productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:91c015eec1fb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://nordicapis.com/8-unexpected-challenges-of-running-an-api-as-a-product/">
    <title>8 Unexpected Challenges of Running an API-as-a-Product | Nordic APIs |</title>
    <dc:date>2021-07-09T00:49:54+00:00</dc:date>
    <link>https://nordicapis.com/8-unexpected-challenges-of-running-an-api-as-a-product/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Developers want to pay only for what they use. Yet, Freyfogle has noticed a stark contradiction: developers want complete pricing predictability, but they are terrible at estimating usage. Within software developer culture, people are “deeply resistant to paying for anything,” says Freyfogle.

Interestingly, in practice, Glickenhouse finds that the bulk of API business potential doesn’t even lie in direct charging, but in indirect models. “This is the real API monetization,” he describes. For example, in some affiliate models, a developer receives payment, acting as an agent for the provider. Therefore, it may behoove API providers to consider what alternative methods or partnerships they could leverage outside of direct monetization.

API providers must consider usage limits, price subscription plans accordingly, and consider how they bundle endpoint access per developer account. With all this in mind, figuring out the financial terms around an API product and proving its success in production may take some time."]]></description>
<dc:subject>apis products monetization</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c7c9f103a9ff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:monetization"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gist.github.com/ramalho/93b87e961b6e019be8e1f6f82864b6f9">
    <title>RethinkDB: why we failed</title>
    <dc:date>2019-09-30T19:13:05+00:00</dc:date>
    <link>https://gist.github.com/ramalho/93b87e961b6e019be8e1f6f82864b6f9</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["When we announced that RethinkDB is shutting down, I promised to write a post-mortem. I took some time to process the experience, and I can now write about it clearly.

In the HN discussion thread people proposed many reasons for why RethinkDB failed, from inexplicable perversity of human nature and clever machinations of MongoDB's marketing people, to failure to build an experienced go-to-market team, to lack of numeric type support beyond 64-bit float. I aggregated the comments into a list of proposed failure reasons here.

Some of these reasons have a ring of truth to them, but they're symptoms rather than causes. For example, saying that we failed to monetize is tautological. It doesn't illuminate the reasons for why we failed.

In hindsight, two things went wrong -- we picked a terrible market and optimized the product for the wrong metrics of goodness. Each mistake likely cut RethinkDB's valuation by one to two orders of magnitude. So if we got either of these right, RethinkDB would have been the size of MongoDB, and if we got both of them right, we eventually could have been the size of RedHat[1]."]]></description>
<dc:subject>postmortems failure failures postmortem databases products productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:be8666feeddb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:postmortems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:failures"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:postmortem"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:databases"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.slideshare.net/launchany/apistrat-keynote-lessons-in-transforming-the-enterprise-to-an-api-platform">
    <title>APIStrat Keynote: Lessons in Transforming the Enterprise to an API Pl…</title>
    <dc:date>2018-10-02T16:11:03+00:00</dc:date>
    <link>https://www.slideshare.net/launchany/apistrat-keynote-lessons-in-transforming-the-enterprise-to-an-api-platform</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>apis products presentation deck slides enterprise</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c9c3665819a4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:presentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:deck"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:slides"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:enterprise"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://matthewreinbold.com/2018/07/10/Update-on-NPS">
    <title>Rethinking NPS for API Quality</title>
    <dc:date>2018-07-10T21:50:38+00:00</dc:date>
    <link>https://matthewreinbold.com/2018/07/10/Update-on-NPS</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Since moving away from NPS, we’ve gone to a much more straightforward average of reviewer scores. While each of these have a high degree of nuance, at a high level APIs are scored on:

Standards Adherence
Completeness of the Documentation
Consistency and Cohesion with Previously Published Work
Viability to Exist as an API Product
The average score remains useful for leadership to know where they are in their API design maturity. But what is much more actionable for teams is directed feedback. A team that learns that their design averaged a score of “6” could cast about for changes to make on their next version. Or they could address a detailed list of concerns.

]]></description>
<dc:subject>nps quality measurement apis products assessment governance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a06ab892e916/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:nps"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quality"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:measurement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:assessment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:governance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://matthewreinbold.com/2018/03/12/ProductManagementInAPIDesign/">
    <title>The Role of Product Management in API Design</title>
    <dc:date>2018-03-13T15:13:36+00:00</dc:date>
    <link>https://matthewreinbold.com/2018/03/12/ProductManagementInAPIDesign/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Building for the Correct Audience
Product managers should understand the audience that will consume the API. That may be easier than it sounds, as there actually several different types of people evaluating an API, each with their own questions. As Brad Fults mentions, these audiences may include, but are not limited to:

Decision Makers evaluating competing API products
Developers looking to get started
Integrators attempting to debug a specific issue in an existing client
Each audience has different needs. For the decision maker, is the functionality provided by an API the same, if not better, than other competitive offerings? Can a developer get started with an API easily, perhaps with nothing more than a CURL statement? Does the API return the type of error messages that, when things go wrong, make it easy for an integrator to fix?]]></description>
<dc:subject>apis productmanagement products</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cae511c26142/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/capital-one-developers/api-product-ownership-is-key-for-api-adoption-6a12c64b2c83">
    <title>API Product Ownership is Key for API Adoption – Capital One DevExchange – Medium</title>
    <dc:date>2018-02-20T18:25:29+00:00</dc:date>
    <link>https://medium.com/capital-one-developers/api-product-ownership-is-key-for-api-adoption-6a12c64b2c83</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[solid post from James Higganbotham]]></description>
<dc:subject>apis products implementation strategy approach bestpractices</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:28655f5a1422/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:implementation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:strategy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:approach"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:bestpractices"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://glutenproject.com/certified-gluten-free-jolly-ranchers">
    <title>YPE html&gt;List of All Certified Gluten Free Jolly Ranchers | The Gluten Project</title>
    <dc:date>2018-02-12T05:14:12+00:00</dc:date>
    <link>https://glutenproject.com/certified-gluten-free-jolly-ranchers</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>gluten glutenfree search products list</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f6c5216d3c0a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gluten"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:glutenfree"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:search"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:list"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.keen.io/platforms-vs-products-8994f4d726c7">
    <title>Platforms vs Products</title>
    <dc:date>2017-03-25T15:55:53+00:00</dc:date>
    <link>https://blog.keen.io/platforms-vs-products-8994f4d726c7</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>platforms products finance comparison</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e705e871ebf2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:finance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://busse.io/who-should-write-the-sample-apps-for-an-enterprise-api-product/">
    <title>Who should write the sample apps for an Enterprise API Product?</title>
    <dc:date>2017-03-03T16:44:51+00:00</dc:date>
    <link>http://busse.io/who-should-write-the-sample-apps-for-an-enterprise-api-product/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>APIs devrel samples products</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9fa9fa19ca2c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:APIs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:devrel"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:samples"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://stratechery.com/2016/how-google-cloud-platform-is-challenging-aws/">
    <title>How Google Is Challenging AWS – Stratechery by Ben Thompson</title>
    <dc:date>2016-12-07T05:24:01+00:00</dc:date>
    <link>https://stratechery.com/2016/how-google-cloud-platform-is-challenging-aws/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[I think this is an idea that can be abstracted to be broadly applicable; indeed, it’s a core piece of Aggregation Theory: as distribution (or switching) costs decrease, the importance of the user experience increases. To put it another way, when you can access any service, whether that be news or car-sharing or hotels or video or search etc., the one that is the best will not only win initially but will see its advantages compound.

This is Google’s bet when it comes to the enterprise cloud: open-sourcing Kubernetes was Google’s attempt to effectively build a browser on top of cloud infrastructure and thus decrease switching costs; the company’s equivalent of Google Search will be machine learning]]></description>
<dc:subject>google aws cloud products platforms competition</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6fb3327b0ccd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:aws"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cloud"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:competition"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@juliamitelman/the-product-manager-vs-the-strategist-49049a8e079f">
    <title>The Product Manager vs. The Strategist – Julia Mitelman – Medium</title>
    <dc:date>2016-11-29T18:46:04+00:00</dc:date>
    <link>https://medium.com/@juliamitelman/the-product-manager-vs-the-strategist-49049a8e079f</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Why, what, how]]></description>
<dc:subject>productmanagement strategy products</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:df312ce62947/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:strategy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://community.apigee.com/articles/2514/how-to-restrict-api-resources-by-their-full-path-a.html">
    <title>How to restrict API Resources by their full path and verb - Apigee Community</title>
    <dc:date>2016-01-15T05:50:28+00:00</dc:date>
    <link>https://community.apigee.com/articles/2514/how-to-restrict-api-resources-by-their-full-path-a.html</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>products edge apigee resources community</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5a5fd0bfb0b4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:edge"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apigee"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:resources"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mcfunley.com/data-driven-products-now">
    <title>Dan McKinley :: Data Driven Products Now!</title>
    <dc:date>2014-09-20T05:19:23+00:00</dc:date>
    <link>http://mcfunley.com/data-driven-products-now</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[via Pinboard Network RSS Improver http://pipes.yahoo.com/pipes/pipe.info?_id=b22b9c9acee5906aab7e8a7645a247a9 this talk on data driven products from a former etsy engineer is good: via/ @mikeolson]]></description>
<dc:subject>iftttFeedly metrics abtesting testing data products driven etsy awesome slides</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ab08680c9272/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:iftttFeedly"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:abtesting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:driven"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:etsy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:awesome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:slides"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.statuspage.io/user-experience-means-more-than-a-good-product">
    <title>StatusPage.io Blog - Good User Experience Means More Than A Good Product</title>
    <dc:date>2013-10-15T23:33:49+00:00</dc:date>
    <link>http://blog.statuspage.io/user-experience-means-more-than-a-good-product</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Our view is that Support is Sales. The goal isn't just to resolve the support issue, it's to get to know the Customer. An easy way to start is by always asking questions in support responses. "What are you building?" "I noticed you work here -- are you looking to integrate X for Y? Things like that." The better you know your customer, the better your product will be."]]></description>
<dc:subject>customers users support products listening community</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:129c005844dd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:customers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:users"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:support"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:listening"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.programmableweb.com/2013/04/16/every-cloud-service-needs-an-api-product-manager/">
    <title>Every Cloud Service Needs an API Product Manager</title>
    <dc:date>2013-04-17T21:32:34+00:00</dc:date>
    <link>http://blog.programmableweb.com/2013/04/16/every-cloud-service-needs-an-api-product-manager/</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>apis products</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1e937ad7a3d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://news.ycombinator.com/item?id=3554206">
    <title>Automate Everything - the hacker way | Hacker News</title>
    <dc:date>2012-02-14T07:36:44+00:00</dc:date>
    <link>http://news.ycombinator.com/item?id=3554206</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""I decided to roll my own in this case because I was interested in learning about email handling after watching this great railscast from Ryan Bates. And because paying $9 per month per user for something I could probably write myself in a couple of hours seemed silly."
I find myself having to fight against this instinct almost every day. There are a couple of problems with hacking for a couple of hours to save a few bucks a month.
Firstly, you now have an additional piece of software to maintain - you're committing yourself to an unknown quantity of future work.
Secondly, your software won't get any better without you actively improving it. The nice thing about software you pay someone else for is that it gets better over time.
It's a tough instinct to fight though. Building things is Fun. It's just that there are probably other things you should be building that are more important to your company."

"As a rough guide, you might factor in another 8-10 hours, because, according to Fred Brooks, a proper programming "product" takes about x3 as long as a "program"."]]></description>
<dc:subject>programming coding webdev hackers products estimates burden maintenance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:899ebd46e63d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:coding"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:webdev"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hackers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:estimates"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:burden"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:maintenance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://kylelacy.com/stop-talking-about-products-and-services/">
    <title>Stop Talking About Products and Services | Kyle Lacy - Social Media Training and Digital Marketing</title>
    <dc:date>2011-10-26T16:35:15+00:00</dc:date>
    <link>http://kylelacy.com/stop-talking-about-products-and-services/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[
                
                    "Stop talking about your products and services as objects and items, and talk more about who and how those products and services are used to do amazing things. Build a culture of accomplishment around your offerings, rather than a culture of availability." from: http://www.convinceandconvert.com/book-reviews/the-power-of-consumer-choice-drives-social-media-importance/
                
            ]]></description>
<dc:subject>quote products services marketing quotes</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4ad47949de04/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quote"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:products"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:services"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:marketing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:quotes"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>