Tag: VRM (page 7 of 8)

EmanciPay: a new business model for newspapers

Rex Hammock is right to gripe about the newspaper turtles pulling their heads in their shells and complaining that readers aren’t paying for the goods papers offer for free online. In that post he runs down some of the drumbeats he’s been hearing:

Here’s the problem with all of those systems: they’ll all be different, silo’d, inconsistent with each other. And doomed to fail for all those reasons.

Here’s the solution: One new system that makes it as easy as possible for readers to pay for the goods, but voluntarily, on their own terms. This new system would turn consumers into customers by giving them the pricing gun. And here’s what’s also cool about it: We’re already working on it at ProjectVRM. It’s called EmanciPay. (Note: when this was written, it was still called “PayChoice”. DS – 1 September 2009)

It’s still early. But it will get a lot less early if some of these pubs stop complaining and put their shoulders (and their wallets) behind work that’s already going on.

A little understanding goes a short way

It’s kind of hard to debunk something before it exists, but that’s what Graham Hill attempts with Four Fallacies of Vendor Relationship Management. Says Graham,

VRM is Doc’s response to the problems of customers getting the rough end of the stick in their dealings with companies. Rather than companies owning huge databases of customer transaction data which they can mine for their own advantage, customers should take control of their own transaction data and selectively release it to companies when they want something from them. Sounds simple enough doesn’t it.

Hard to know where to begin here. But I’ll try.

  1. VRM is not just my response. Many are involved in thinking about VRM and developing code and products to make it happen. It’s also still early. There is no code out there to critique yet.
  2. VRM is not just about “the problems of customers getting the rough end of the stick in their dealings with companies”. That’s just one corner of a much large set of problems VRM will work to reduce. Another is poor and not very granular vendor intelligence about what customers actually want. Another is a lack of a uniform and consistent way for customers to manage relationships with multiple vendors. Another is the blindered way that vendors look at “the customer” as a template rather than as an individual, denying vendors much information that might be useful. Another is money left on the table because there is no good way for customers with money to spend to notify whole markets of their wants, in ways that protect the customer’s privacy at the same time. Shall I go on? I can, but I’m not sure it’s worth it.
  3. Where did I, or anybody, say “Customers should take control of their own transaction data and selectively release it to companies when they want something from them”? Yes, VRM will give customers ways to control their own data, to serve as the point of integration for that data, and to share that data in selective and cooperative ways with vendors. “Take control” makes VRM sound like it’s a way for customers to storm the walls of Fort Business. That’s not the idea. Instead the idea is locating data where it makes the most sense, and giving those controlling customer data better ways of applying it. Data about who we are, what we want, where we live, how we do business … Much of this should live on both sides of the relationship system.  Data “ownership” is a sticky and complicated issue. For VRM’s purposes, however, “owning” does not mean wrestling data away from vendors.

Bottom line: VRM is about providing customers with tools that make them both independent actors in the marketplace and better equipped to engage with vendors. Those tools are in development. We need to get some of them out there before we can even begin to have arguments about whether or not they’ll work. Fact is, they will or they won’t. But they deserve a chance before we go salting the soils in which they need to grow.

Graham goes on to list “four fallacies”:

  1. The Fallacy of Ceding Control
    Fallacy One: Companies are just not going to cede control over customers’ data.
  2. The Fallacy of Wanting Control
    Fallacy Two: Customers way want more control over the marketing which is sent to them, but not their actual transaction data.
  3. The Fallacy of Managed Markets
    Fallacy Three: The customer-managed market upon which VRM is built is not viable.
  4. The Fallacy of the Economic Model
    Fallacy Four: There is not a viable economic model underneath VRM.

First, we’re not asking companies to give up data they control. We’re creating ways to share data that will be tood both sides of the relationship. This will take time. It will also probably follow the same realization and adoption curve as open source code acceptance has followed in enterprises.

Second, customers should want control over their sides of relationships with others. Those relationships should include vendors. VRM is not just about controlling (or restricting) marketing stuff that vendors send out, nor is it just about transaction data. Both are relatively small potatoes. What matters are actual customer wants and needs, along with seemingly trivial yet important stuff, such as having a way of gang-notifying many organizations (inluding vendors) that one’s address has changed, instead of notifying one at a time.

Third, we need to get stratight what “free market” we’re talking about  here. Graham writes, “VRM seems to rest on the assumption that it offers a superior way of deciding what products, services and expeiences to offer to customers than the current free market system.” That’s not correct. VRM rests on a number of assumptions, none of which is that. One of them, however, is that it’s good for vendors to know what customers actually want rather than just guessing about it. Huge amounts of money are wasted by vendors on guesswork. Reducing that would be a nice payoff, wouldn’t it? I think Graham believes we’re a bunch of socialists or something. Far from it. Many of us are free-market advocates of the first order. Not that it should matter. Good ideas should stand in their own proven pudding. We don’t have that yet. Just wait.

Fourth, there is no new economic model underlying VRM. Graham writes, “The free market system has driven unprecedented prosperity in those allowed to participate in it too. I don’t see many people queueing up to enter into planned market economies these days? Why throw all that away for a transaction cost heavy model whose economics hasn’t even worked out, let alone tested and proven?” Two problems here. One is that Graham assumes that VRM opposes the free market system, or that it advocates a planned market economy. It does neither. In fact, we look forward to taking advantage of the free market system by getting better information into it. The other is that Graham seems to assume that the free market and the mass market are the same thing. They are not. The free market encompasses the mass market but is not reducible to it. VRM will improve both the mass market and the market for more individuated products and services.

At the end Graham adds,

Whilst I agree in principle that customers need to be given much more control over how they are managed by the companies they transact with, there are already partial solutions in existence such as customer managed relationships, multi-sided markets and even infomediaries, that enable this. VRM is an extreme solution that no-one is really looking for. Not Customers, not companies, not markets, no-one.

Well, as it said here years ago, CMR wasn’t getting traction (at least as a name). Frederick Newell’s Why CRM Doesn’t Work was one of the first places CMR was put forth (and very well too). But it’s a non-starter as long as it’s coming from the sell side and trying to lock in the customer. Adriana Cronin-Lukas unpacks that problem very well.

Multi-sided markets are very well aligned with VRM. Thanks to Graham for reminding me to contact Andre Hagiu here at Harvard to talk about that.

I’m also a fan of John Hagel and infomediaries as a concept, and I think both are well-aligned with VRM as a concept.

Will VRM succeed where those other ideas are languishing, or support them in some ways? I dunno. Hope so. Meanwhile, I want to offer an olive branch.

Graham is a veteran of the CRM business. It is essential that CRM folks know that VRM is not opposed to CRM. VRM gives CRM systems more to relate to. It gives customers means for bearing some of the relationship weight — ways that work in consistent ways across many vendors, for the conveniences of both sides. So it’s VRM + CRM, not VRM vs. CRM. Unless we make it the former, it won’t work. And it is essential right now to make clear that VRM is a CRM-friendly movement.

Finally, this whole exchange illustrates why I’ve been reluctant to publicize VRM in the absence of working code, working products and working services. It’s impossible not to talk about it, of course, because VRM is a movement with a growing number of people who need to be able to think and talk about it. So here we are. I hope Graham and others will look more carefully, and with more open minds, at what we are actually doing, and cut us a bit of slack while we talk about it in the meantime.

What’s completely screwed about this picture

So I got an email today from Forbes, with the subject “You are Important to Us”. It says this:

Dear Subscriber:

Forbes values you as a customer and your opinions are very important to us.  We are conducting a study and would like to include your opinions.

The survey will take about 10 minutes to complete and we think you’ll find it interesting and enjoyable. Your responses will be used for research purposes only and will be held in the strictest confidence.

Simply click on the link below to visit our survey.

Click here to take the survey [The link goes to a long address that begins http://forbes.puresendmail.com/print.]

Again, we thank you so much for participation.

Sincerely,

Bruce Rogers, Chief Brand Officer – Forbes

You are receiving this email because you registered at Forbes.com LLC. and signed up to receive third party emails To manage your preferences or change your delivery address, please click here.

You may also email your opt-out request to  privacy at forbes.net or send your request in the mail directly to:

 Forbes.com LLC

Attn: Privacy Administrator
90 5th Ave. 6th Floor
New York, NY 10011

To review our privacy policy click here.

Copyright 2008 Forbes.com LLC TM

I thought, “Hey, I’m busy, but I like Forbes, and I’m inclined to cooperate, even if I hate most surveys and would rather relate to Forbes in a less one-sided and impersonal way. So I punched on “Click here to take the survey”.

The first step was one that asked me what my title was. I have several, but none of them are from the lexicon of corporate hierarchies. So, next to “other” I wrote “fellow”. Because that’s what I am, here at the Berkman Center. (I’m also Senior Editor of Linux Journal and President of my own small company, but I went with “fellow” because I get Forbes where I live near Berkman and not at my home office in California.)

The first survey page told me the thing would take about ten minutes. That’s a lot, but I thought, “Okay, I’m still game. Let’s see how fast we can make this.”

It was over in one second. Or however long it took for the survey server to send me to a page with the title “Thank You – InsightExpress.com“. Its entire contents were this:

Return to Your Originating Web Page

I hit the back button and it went nowhere. Then I clicked on the address in the email. That timed out. So did I.

This is the point at which one might be tempted to write to Bruce Rogers or the nameless  Privacy Administrator, but Forbes has gone out of its way here to avoid human contact (no email address for Bruce, a surface mail address for ATT:Privacy Administrator — both of which scream “WE ARE AVOIDING YOU. PLEASE COOPERATE.) But that would be weak and supplicating, and I have no interest in being either. I’d rather be the good Forbes subscriber that I’ve been for years and attempt to make constructive human contact instead.

I’ll do that three ways. First is with the headline above, plus links and other bait that might get the attention of Bruce Rogers or one of his factota. [Note: I posted this at 1:12pm, and Bruce responded personally at 1:56. Well done!] Second is with an email to some folks I know at Forbes. Third, and most importantly, I’ll try to explain the VRM angle on this.

VRM is Vendor Relationship Management. It’s how customers manage relationships with vendors. (Or with other individuals, or with organizations of any kind — such as churches or governments.)

Most vendors are familiar with CRM, for Customer Relationship Management. I can’t tell if a CRM system was involved in this little exchange, but a failure of this kind is certainly within the scope of CRM’s concerns. (To visit those, check out the CRM sites for SAP, Oracle, SalesForce, Amdocs and Microsoft, which are the top four companies in an $8+ billion business.)

Right now VRM is a $0 billion business. But in the long run it’ll be big, and it’ll improve the CRM business along with it, because it’ll give CRM something more substantial than mailing addresses to relate to.

A number of development communities are working on VRM solutions right now, but rather than talk about those I’ll just say what I’d like here. Not from Forbes, but from VRM developers. If Forbes or any CRM companies want to help with that, cool.

I would like a simple dashboard that tells me what I’m subscribed to and what I’m not — both for print publications such as Forbes and for email subscriptions of every kind. I would like to have global preferences that would govern how I relate to each of those publishers, and how they relate to me. For example, I would like to throw a switch that says “No” to all third party mailings, both to my font door and to my email addresses. When I establish a relationship with a new publisher, or publication, or supplier of any kind, I would like them all to know, as a matter of policy, that I don’t want them to waste their time, money and server cycles by sending me junk mail of any kind. And that I don’t appreciate having my own bandwidth, cycles, disk space, rods, cones and time wasted dealing with any of it. I might give a global or selective thumbs up to surveys, provided I also have a standard way to send error messages and other feedback to survey sources.

On the positive side, I would also like to open conduits through which productive interaction could take place with the publishers, authors and circulation officials whose “content” I pay to get. (And even those that I don’t pay.) I would like a simple, straightforward, universally understandable way to do this, across all “content providers”, so I don’t have to relate only inside each provider’s silo. (By the way, we’re already working on change-of-address, to pick just one subcategory of subscriber-publisher interaction that can be a pain in the butt for everybody. That last link is a working draft, by the way. More work is happening off-wiki.)

That’s just one part of what we’re doing at ProjectVRM. But it’s one I’d like the “content providers” and CRM folks out there to know about. Because it’s going to happen anyway, and I’d suggest getting interested, and perhaps also involved, sooner rather than later.

The architecture of scaffolding

We’ve had a lot of discussion, both online and off, about the V in VRM. It speaks one kind of relating, in the economic sphere. Which is just one sphere.

Britt Blaser has spoken often of the kind of RM that begins with a G — GRM for Government Relationship Management.

We’ve also talked about why we start with the individual in our work with VRM. Why not start with groups, and group empowerment? Especially since “social” is such a hot theme?

The answer is that relating starts with individuals. Even though it always involves more. One’s relationship with one’s self may be interesting to a shrink, but it’s too small for building a society, an economy, a politiy.

Erik Cecil, a friend and freshly minted blogger, almost poetically captures something about relating in this paragraph from his latest post:

IntERdependence is the engine of democracy; it creates the nanostructures of new economies.  People lined 137 miles of railroad track, therefore, not to see some new Hercules.   They came to see in their new President a reflection of their individual importance reflected back to them in the President they just elected.   He not only moved the power of democracy to the edge, but opened the path back to the middle.   Reverberating throughout the crowds was the music of interdependence.  Let the new freedom ring.

We’re in new territory here — one we’re just beginning to make for ourselves.

Creating a market force

So I’ve been asked (somewhere… can’t find it right now, so maybe one of ya’ll will remind me) if the last three paragraphs of this post by Daniel Goleman speak in some way to VRM. Here they are:

The singular force that can drive this transformation of every manmade thing for the better is neither government fiat nor the standard tactics of environmentalists, but rather radical transparency in the marketplace. If we as buyers can know the actual ecological impacts of the stuff we buy at the point of purchase, and can compare those impacts to competing products, we can make better choices. The means for such radical transparency has already launched. Software innovations now allow any of us to access a vast database about the hidden harms in whatever we are about to buy, and to do this where it matters most, at the point of purchase. As we stand in the aisle of a store, we can know which brand has the fewest chemicals of concern, or the better carbon footprint. In the Beta version of such software, you click your cell phone’s camera on a product’s bar code, and get an instant readout of how this brand compares to competitors on any of hundreds of environmental, health, or social impacts. In a planned software upgrade, that same comparison would go on automatically with whatever you buy on your credit card, and suggestions for better purchases next time you shop would routinely come your way by email.

Such transparency software converts shopping into a vote, letting us target manufacturing processes and product ingredients we want to avoid, and rewarding smarter alternatives. As enough of us apply these decision rules, market share will shift, giving companies powerful, direct data on what shoppers want — and want to avoid — in their products.

Creating a market force that continually leverages ongoing upgrades throughout the supply chain could open the door to immense business opportunities over the next several decades. We need to reinvent industry, starting with the most basic platforms in industrial chemistry and manufacturing design. And that would change every thing.

It’s certainly consistent with VRM. And the first four words of the last paragraph are exactly what we expect VRM to do.

VRM in 2009

This blog is #19 and Chris Carfi’s Social Customer Manifesto is #7 on Chris Bucholtz’s Best CRM Blogs of 2008, at Inside CRM. About this blog, Chris wrote,

The bumpy economy has perhaps been unkind to forward-looking philosophies like vendor relationship management, but that has not curtailed Searls’ explorations of what will be when the business world finally understands that the customer is now running the show. He makes a convincing argument that companies are leaving dollars on the table already by refusing to admit that this is a consumer-driven world. As Searls wrote, “I’d rather have ‘-driven’ than ‘-centric.’ Because being ‘-centric’ doesn’t require you to relate. Being driven does.”

I never thought about this as a CRM blog, but to the degree that CRM and VRM will work together, it makes sense.

It will be interesting to see which CRM companies realize that customers are driving with VRM. Some are already waiting to see VRM tools show up in customer hands. At a recent ProjectVRM committee meeting, one of the attendees from a CRM company reported that the top honcho at his outfit said “Whoever wins at VRM wins at CRM.” That’s good to hear. VRM will give CRM much more to engage with.

Anyway, Larry Dignan seconds Paul Greenberg’s expectation that 2009 will be VRM’s breakout year. He adds this:

Simply put, a VRM tool would be something customers use to relate and manage multiple vendors. Greenberg thinks that 2009 will be the year in which VRM becomes more than just a concept. What’s ironic is that vendors that have the most tentacles into companies (Oracle, for instance) may become players. Just imagine the following: here’s a VRM tool from a big vendor so you can better manage it.

Well, if the tool only helps you manage one vendor, it’s not a VRM tool. But the irony risk is not small. That’s why I’m still not eager to promote VRM before we have working code and ways of demonstrating how VRM tools make you both independent of vendors and better able to engage with them.

May the best customers win.

Relationship in markets

Back after The Cluetrain Manifesto came out — first as a website (March, 1999) and then as a book (January 2000) — some of the best feedback came from people in what people used to call the Third World (that was before the first two merged into one, and a bunch of countries in the third group joined in). What it boiled down to was this: “‘Markets are conversations’ is a pretty bright thing for you First Worlders to say, but it’s old hat with us. Your next job is to understand how markets are about more than both transactions and conversations. They’re also about relationships.”

So that’s a setup for quotage from JP Rangaswami. Noting that a fellow twitterer said the word “reputation” is so 1990. today it’s all about relationships, JP added,

Maybe it’s the Calcuttan in me, but I guess I’ve always thought that way. For me, it’s always been all about relationships. Relationship before conversation before transaction. But as the Cluetrain guys so elegantly pointed out, that sequence had been lost in the West, and society had become more about Transaction First, Conversation only if it is going to help Transaction, Relationship only if it is going to help Conversation (and therefore Transaction).

No surprise then that when Customer Relationship Management systems came out, they tended not to be about managing customer relationships, but about managing transactions and exploiting the customer. Because they were deeply rooted in Transaction First.

… and did their best to exclude conversation as well.

Later he adds,

Relationships are about abundance, not scarcity. Provided they are nonhierarchical, of course. That’s what the people who discovered network effects understood, that relationships scale differently, create value differently. Reputation is deeply intertwined with relationship, reputation is an embodiment of what your relationships say about you. So reputations should also be about abundance, not scarcity. And can enjoy network effects as well.

In the past, even in the West, this so-called “Eastern” concept of reputation was understood. Relationships did come first, then conversation, then transaction. It has been lost. Over the last twenty years or so, it is being re-found.

I’m not sure relationship — the real kind — scales. That’s obvious to me every time I open Facebook and find myself on the receiving end of hundreds of requests for me to declare my friendship with acquaintances. Follow me on Twitter if you like, and I might follow you back; but don’t expect me to “relate” in every case.

The relating we’re talking about with VRM is of both an old and a new sort, I think.

The old sort is personal. It’s something I as an individual have, and control. I believe The Mine Project does this.

The new sort is about relating as much or as little as one needs to, with vendors and other entities out in the marketplace. What matters is that you as an individual are in control, and relating — engaging for purposes beyond transaction or conversation — is the purpose.

I have much more to say about this, but need to leave my hotel and get on the first of two planes from San Francisco to Boston. More later.

Answering tweeted questions about VRM

So, with the help of vangeest and Twitter Search for #vrmevent, I’m addressing questions tweeted from the virtual floor here at the VRM Event in Amsterdam. Here goes…

vangeest: @dsearls: retweet @vangeest: #vrmevent: what is the relationship between the good old B2B marketplaces like Ariba and VRM?

As an idea VRM owes something to B2B, for the simple reason that B2B relationships tend to be between equals. Thus they can be rich and complex as well. B2C tend to be simplified on the B side, mostly so maximum numbers of templated Cs can be “managed”. Iain Henderson has talked about how there are thousands of variables involved in B2B VRM, while only a handful with CRM, which is B2C.

VRM essentially turns B2C into a breed of B2B — to the degree that both terms no longer apply. VRM equips individuals to express their demand in ways that B2C never allowed, and B2B never included.

But VRM is not a site, or a marketplace. That makes it different from Ariba, eBay, or online marketplaces. VRM may happen inside of those places, but VRM is not about those places.

Most importantly, VRM is not something that companies give to customers. It’s something customers bring to companies.

zantinghbozic: #vrmevent ichoosr: vrm is socialism 2.0 – http://mobypicture.com/?pcg0qr

This reports a provocative tease by Bart Stevens of iChoosr in his opening slide. I don’t agree with the statement, but his deeper point rings true: it involves a shift in power in the marketplace, from producers to consumers. Except I wouldn’t use the word consumers. I’ll explain that later.

Can we fix travel?

Two parts to my theory here.

One is that the airline business is sucky for reasons the airlines can’t fix by themselves.

The other is that only customers can fix it for them.

The reason airlines are sucky is that they treat customers as cargo rather than as human beings. Of course they don’t think and talk that way, but that’s what it comes down to. Cargo comes in a limited variety of shapes, sizes and routing needs, and passengers are treated accordingly.

The problem is that passengers are human beings. All human beingss are different. That’s why they look different, have different fingerprints, different DNA, different interests and proclivities, and so on.

There are certain identicalities that need to be factored in, of course. We’re all likely to be wearing clothes, able to communicate, and have to go to the toilet every once in awhile. We have minimum needs for comfort and service. But after that the variations go way up.

But big businesses such as airlines need to keep the variables down for the sake of efficiency alone. So they make templates of travelers and choices, and try to match those up. All businesses do this to some degree. (Even health care, as I discovered earlier this year.)

Some, such as I, are travelers (frequent in my case) who have peculiar needs that are actually not hard to fill. In particular I want a window seat away from the wing. I would like to be able to look for the seat I want on any airline.  I am willing to select an airline based on being able to get the seat I want, and I am willing to pay something extra for that, even if it’s with an airline I don’t frequently fly.

This “something extra” is money left on the table right now. I am certain there are plenty of flyers with requirements just a unusual as mine.

Today airlines are starting to charge extra for the variables they know well: food, for example, and seat changes. US Airways, which I flew a couple times recently, charges even for water, and for seat changes. While I’m unlikely to pay for those, I am likely to pay for getting the seat I want in the first place.

On United, where I am a IK (greater than 100,000 miles per year) flyer, I get some privileges, which I appreciate; but none of them include being able to upgrade to a seat I want on business class. Since in most cases I already have a seat chosen in economy class, I won’t put in for an upgrade, because I can’t specify seat preference. United assumes that all business class seating is desirable, so they don’t bother with that, unless you’re asking in person at the counter or the gate at the airport. So I usually go without the upgrade. The money left on the table here is what I’m willing to pay for a window seat in business class. It’s a lot more than nothing. It’s even more than the frequent-flying certificates I usually accumulate and spend for upgrades.

What we need to create are the means by which flyers store and publish their preferences, in forms that airlines can see and address if they like. This is just one example of what can be done with a combination of personal data stores, selective disclosure, and policies set personally rather than corporately — policies that can be read in a standard way and acted upon.

What’s key is that the customer needs to be the point of integration and origination for his or her own data, and that he or she have selective control over the disclosure of personal requests and requirements, with clear terms of use and service.

None of this would have come up for me if I hadn’t just had an unhappy experience talking with Lot Polish and Swiss airlines. I’ll be flying on both in the coming weeks. I booked them through United, which is a partner of theirs through Star Alliance. (I am “Star Alliance Gold”, for what that’s not worth.) But because I did not book with them, they refuse to give me any choice of seats except at the gate. This not only sucks, but makes me not want to fly on those airlines. I assume they do this stuff to subordinate flyers from other airlines to frequent flyers on their own. But I don’t know. All I know is that, given a choice in the future, I won’t be flying with them.

Anyway, I’ll be in the UK from Sunday to Wednesday, and will be talking with VRM folks over there about all kinds of stuff, including the ideas I’m floating here.

Looking forward to seeing many of you at the VRM Hub on Monday.

Portable Contacts API and VRM

The looks to me like it could (and maybe should) be one of the open source building blocks for VRM. Read this piece by David Recordon, and watch this video. If you love energetic hack-a-thons (and you should; much of the code we all use was born in these fecund environments), there’s much to be encouraged about.

Key excerpt:

Joseph Smarr and Kevin Marks of Google hacked together a web transformer that integrates Microformats, vCard, and the Portable Contacts API. Given Kevin’s homepage which is full of Microformats, they’ve built an API that extracts his profile information from hCard, uses a public API from Technorati to transform it to vCard, and then exposes it as a Portable Contacts API endpoint. Not only does this work on Kevin’s own page, but his Twitter profile as well which contains basic profile information such as name, homepage, and a short bio.

Brian Ellin of JanRain has successfully combined OpenID, XRDS-Simple, OAuth, and the Portable Contacts API to start showing how each of these building blocks should come together. Upon visiting his demo site he logs in using his OpenID. From there, the site discovers that Plaxo hosts his address book and requests access to it via OAuth. Finishing the flow, his demo site uses the Portable Contacts API to access information about his contacts directly from Plaxo. End to end, login with an OpenID and finish by giving the site access to your address book without having to fork over your password.

I suggest lining up a session or two at IIW to connect the Portable Contacts API and related VRM work on items such as personal data stores.

Thoughts and connections in the meantime are welcome as well.

Hat tip to Keith Hopper.

Older posts Newer posts

© 2023 ProjectVRM

Theme by Anders NorenUp ↑