Building a Global/Local Platform with Etsy

In a recent and very informative fireside chat, Linda Kozlowski, COO of Etsy was in conversation with Sarah Moran, CEO of Girl Geek Academy. Key themes of the discussion included the challenges in building a “global/local” platform, making sure you are addressing the right audience needs, and in a two-sided market place, knowing how to balance the interests of sellers and buyers.

etsyOrganised by StartupVic and hosted by inspire9, it was yet another example of how fortunate Melbourne is to attract and host so many leading global figures in the startup world, willing to share their insights (as well as learn more about the local startup scene – which probably does not get as big a rap as it should, especially in mainstream media).

With previous operational roles at both Alibaba and Evernote, Linda brings a strong combination of experience in tech and market places, and describes her current position as covering “CX and revenue from end-to-end”. Her primary focus is on product development, global expansion and addressing sellers’ problems.

At Etsy, the aim is to develop a global product platform that is culturally diverse. There is a natural tension between fully localised customisation (which can be costly to maintain – translation, version control, managing updates), and a “best of breed” model that can serve most users (which can lead to too many compromises). So instead, Etsy pursues a strategy of locally originated products and features, combined with open APIs.

Etsy has also identified sellers as their core audience. This means that so much of the CX is actually determined by sellers’ needs, to whom Etsy then serves up customers to the platform via social media, content marketing and SOE. Etsy sees this as a point of differentiation when considering traditional retailers who often end up squeezing their suppliers on pricing and margins.

In balancing the needs of two-sided markets, again Etsy focuses on the seller first – because buyers want to see depth of inventory and a range of quality products, so get sellers on-board and the buyers will come.

Asked how Etsy avoids buyers going direct to suppliers, Ms Kozlowski commented that it all really depends on where transactions happen: make the CX is so sticky that sellers want to stay on the platform, offer great seller features, and bring in quality buyers. On the other hand, it’s a healthy market place, so there is no mandating or exclusivity – because of course, successful sellers will sell in multiple places.

Etsy believes in investing in the right technology and the right marketing at the same time. For example, although the business was started in 2004, Etsy only began brand marketing in 2016. The types of marketing deployed include storytelling, identifying key differentiators, understanding customer influences, extensive content strategy, plus performance marketing (site traffic, SEO) to see what else customers may be looking for. According to Ms Kozlowski, a retail site should spend about 20-30% of revenue on marketing, otherwise you are buying traffic and customers (red flag to investors!) Alternatively, establish some ROI goals for marketing costs, especially performance marketing, and during the startup phase (up to 1 year) begin with 15-20% of revenue.

At the heart of Etsy’s business model is an evolving technology and e-commerce platform that allows micro-businesses to run at scale. The USP is a community of network effects: 1.7m sellers, 27m buyers, 40m products, 12,000 “teams”, whose “captains” recruit other sellers. (Australia is actually in Etsy’s Top 5 markets.) In addition, Etsy aims to act with integrity in respect to dispute resolution and addressing fraud – they use machine learning to detect rogue sellers (although often, buyer disputes are a reflection of seller inexperience, rather than fraudulent behaviour). Etsy also offers training and support to resolve disputes, and the community is very good at policing itself.

What are some of the unexpected challenges of market places? When it comes to distinguishing between commodity items and unique creative products, technology will under-price and displace commodity goods that are easily made. It’s also important to build human-to-human connections, and to have a global perspective – for reasons of quality and diversity, and not self-limiting your business, especially when it comes to managing different market and economic cycles. Remember to “follow the data”, and anticipate demand and trends. Among some of the technology challenges, dealing with different devices in different countries can be an issue.

In conclusion, Ms Kozlowski offered some advice for anyone thinking of launching a market place:

First, consider why there are very few local e-commerce markets in Australia (from my personal perspective it’s a complex mix of retailers getting burned in the dotcom boom/bust, cosy market duopolies, and perpetual geo-blocking…). But let’s not forget that Alibaba has just opened its Australian & New Zealand HQ in Melbourne, likely to ruffle a few feathers in the retail sector.

Second, embrace a local/global mix (for the reasons mentioned above)

Third, don’t price too low (although Australia is notorious for being a “price-sensitive” market…).

Finally, the conversation ended with a tantalising glimpse of “the future consumer” (Gen Z) where makers connect directly with buyers.

Next week: Spaceship launches the future of superannuation

Gigster is coming to town….

Melbourne’s Work Club recently hosted Gigster Senior Project Engineer, Catherine Waggoner, in conversation with Venture-Store’s George Tomeski. Part of Startup Victoria‘s Fireside Chats, it likely herald’s Gigster opening an office in Melbourne, to service local clients and to tap into the local developer community.

gigsterFor the uninitiated, Gigster describes itself as the “world’s engineering firm”, that helps clients scope, design and build software, apps and digital products. Using an established product development methodology, and drawing on the resources of a 1,000 strong network of freelance designers, developers and product managers, Gigster is taking much of the pain out of the costing and requirements process for new projects, as well as building a growing client base of enterprise customers.

Not mincing her words, Ms Waggoner opened her remarks by commenting, “The software development industry model is f*#$ed”, because:

  • Requirements are poorly defined
  • Scoping is laborious
  • Development costs blow out, and
  • The whole process is not very transparent and not very accessible.

As a case in point, she mentioned the significant cost disparity between what some digital design agencies or app studios might quote for building an iOS product compared to what Gigster would estimate. By: breaking projects down into the distinct stages of scoping, design and pre- and post-MVP; only engaging the “best of the best talent”; using proprietary tools both to estimate fixed rate costs (rather than billable hours) and to define and source solutions; and re-using content from a library of “Community Software” resources, Gigster is able to deliver quality projects in shorter time, and on more modest budgets. For example, based on the large number of projects that they have fulfilled, their “Gigulator” estimating tool incorporates 5,000 possible features.

From an investor perspective, Mr Tomeski mentioned that the “VC inflexion point is getting much earlier” in tech startups. Meaning, with lower development costs (and potentially, reduced valuation multiples), investors are looking to get in sooner, with lower exposure, but still generate reasonable returns on exit, thanks to cheaper establishment costs.

Of course, Gigster sits at the heart of the gig economy, a huge issue when it comes to discussing the Future of Work. Interestingly, many of Gigster’s contractors are themselves startup founders, who freelance while building their own businesses. But such is the strength of the network, something like 35%40% of their contractors work full-time for Gigster – they like the flexibility combined with the continuity. Many of the contractors are referrals from existing team members, and a number of teams (known at Gigster as “houses” – presumably a frat thing?) have bonded to such an extent that they get allocated specific projects to work on together, even though they themselves may be working in different locations, based on previous projects.

Working for Gigster is probably a career choice for some contractors, because there is a variety of projects to work on, and the opportunity to be involved from start to finish. Which may be the opposite if working in a more corporate or enterprise environment, where work may be routine, repetitive and reasonably narrow in scope.

If Gigster does decide to set up shop in Melbourne (with encouragement from
InvestVictoria) they will be joining the likes of Slack, Stripe and Square, tempted by financial and other incentives. Such a move may challenge a number of local digital agencies, who will face even more competition for talent and customers.

According to Ms Waggoner, enterprise clients represent 40% of the business, and should comprise 60%-80% very soon. Not only that, but the average deal was initially $15k, now it’s more like $100k. However, enterprise clients have a much longer sales cycle. Plus, many innovation teams within enterprises are more like loosely formed groups of niche experts, so they need training on how to think like a startup. When you consider the greater dependency on legacy software by corporate clients (where it may make financial sense to retire some assets and build afresh, but the emotional disruption can be huge…), combined with the greater emphasis placed on after-sales service, Gigster has had to adapt its business model accordingly.

But Gigster must be doing something right. They’ve stopped outbound marketing and prospecting, relying on in-bound leads, repeat business and client referrals. There has been a shift from a sales focus to a customer focus, complete with a dedicated customer success team.

A number of audience questions related to getting VCs interested in your idea: What do they look for? How do they assess opportunities? How far should you go in building a product before you can attract funding? What’s the best way to validate an idea? etc. Much of this is about product/market fit, building the right team, getting customer traction, and executing on your strategy (aka Product Development 101.) As part of her closing comments, Ms Waggoner noted that unlike some of the high-profile VC funds (e.g, Y-Combinator, Techstars and 500 Startups) many VCs are becoming more sector specific, because they prefer to invest in what they know and understand.

Next week: Building a Global/Local Platform with Etsy

Design thinking is not just for hipsters….

In recent months, I have been exploring design thinking, a practice I first encountered nearly 20 years ago (when it was called user-centred design). Whether we are talking about UX/UI, CX, human-centred design, service design or even “boring” process improvement, it’s important to realise that this is not just the domain of hipsters – everyone can, and needs to understand how these design thinking techniques can build better product and service outcomes in multiple applications. Here are three real-world examples to consider:

Curved Space-Diamond Structure by Peter Pearce, Hakone Open-Air Museum, Japan (Photo © Rory Manchee, all rights reserved)

Curved Space-Diamond Structure by Peter Pearce, Hakone Open-Air Museum, Japan (Photo © Rory Manchee, all rights reserved)

1. Financial Services – a case of putting the cart before the horse?

A major bank was designing a new FX trading system, to replace a labour-intensive legacy system, and to streamline the customer experience. The goal was to have more of a self-service model, that was also far more timely in terms of order processing, clearing and settlement.

The design team went ahead and scoped the front end first, because they thought that this was most important from a customer perspective (and it was also a shiny and highly visible new toy!). However, when I heard about this focus on the front end, I was prompted to ask, “What will the customer experience be like?” By automating the process from a front end perspective, the proposed design would significantly diminish the need for customer interaction with relationship managers, and it meant they would have less direct contact with the bank. Whereas, part of the bank’s goal was to enhance the value of the customer relationship, especially their priority clients.

Also, by starting with the front-end first, the design did not take into account the actual mechanics and logistics of the middle and back office operations, so there were inevitable disconnects and gaps in the hand-off processes at each stage of the transaction. (This is a common mistake – a colleague who consults in the retail sector told me about the online storefront for a major retail chain that looked really pretty, but revealed no understanding of the established supply chain logistics and back-office order fulfilment processes.)

The bank team had a rethink of the storyboarding and workflow analysis, to make sure that the customer experience was streamlined, but that there were still adequate opportunities for customer touch points between client and relationship manager along the way.

2. Construction industry – inside and looking inwards

Another colleague told me of a specialist supplier in the construction industry, that was undertaking a review of their processes and service design model. From an internal perspective, everything looked fine. The customer orders came in, they went into production, and were then delivered according to the manufacturing schedule.

However, there were two stages in the process, that did not work so well from a customer perspective:

First, customers did not receive any confirmation or acknowledgment that the order had been submitted; so they might be worried that their order had not been received.

Second, once the order had gone into production, there was no further customer communication until it was ready to be delivered. Meanwhile, the client’s own schedule might have slipped, so they might not be ready to take delivery (we’ve all seen those moments on “Grand Designs”). Resulting in the supplier having to hold unpaid for work-in-progress in their warehouse.

For the supplier, it was a simple case of implementing a formal acknowledgment process, and a check in with the client prior to fabrication and a follow-up prior to delivery to make sure schedules were aligned.

3. Energy sector – gaining empathy in the field

A friend of mine ran a local distribution and installation business for an international supplier of energy switching gear. They specialised in remote operating systems, most notably used in indigenous communities. Head office was in Europe, and the clients were in outback Australia – so communications could be challenging. The overseas engineers would not always appreciate how time critical or simply inconvenient power outages or interruptions could be. “We’ll fix the software bugs in the next upgrade,” was usually the response.

Then the local business started inviting their European colleagues to come and work in the field, to get some downstream experience of how customers use their products. It was also a good opportunity to train technical staff on how to handle customers.

One time, a visiting engineer was in a remote community, trying to fix a power operating system. When Europe said they would take care of it in the next upgrade, the engineer pointed out that he was with the client there and then, and that without power, the community could not function properly, and that Head Office had to solve the problem immediately, even if it meant working overnight. The issue was sorted right away.

If nothing else, the visiting engineer, schooled in siloed processes and internal systems at Head Office, had managed to gain empathy from working directly in the field.*

While none of these examples seems to involve cutting edge design thinking, they do reveal some fundamental service design and product development concepts: the need for empathy, the value of prototyping and testing, the role of user scenario and workflow analysis, and the importance of challenging existing processes, even if they seem to be working fine on the inside.

*Footnote: This reminds me of a time many years ago when I was travelling around Beijing in the back of a cab, between client visits, calling my production team in the US, asking them to investigate a problem the local customers were having in accessing our subscriber website. “The Chinese government must be blocking the site”, I was told. Given that most of the clients were state-owned enterprises, or government departments, I thought this was unlikely. Turns out that the IT team in the States had “upgraded” the SSL without informing anyone and without doing multiple site testing first. Some clients had problems logging on from slower internet services, because the connections timed out. Being in the field, and speaking directly after witnessing the client experience for myself enabled me to convince my colleagues of what the cause actually was. Although we had to implement an interim workaround, going forward, every software upgrade or product modification was benchmarked against multiple test sites.

Next week: More on #FinTech, #Bitcoin and #Blockchain in Melbourne

Change Management for Successful Product Development

Recently, there have been a number of commentaries on the current trend/fad for applying Agile and Lean product development methodologies to corporate management. I’ve also noticed an increasing focus on “Product Management” as a formal discipline by training and professional development providers. Consequently, I’ve been revisiting some work I did many years as part of a Change Management Diploma.

Situational Leadership

My thesis is that different Change Theories of Management can be applied to each stage in the Product Development Cycle*, to ensure that the organisation is aligned with the business needs as they relate to strategy, capabilities, capacity and execution. This is also the context in which organisations use Situational Leadership techniques to cope with constant change in technological, social, economic and environmental forces.

(*This work was based on a reading of Theories of Organisational Change as Models for Intervention by Dunphy & Griffiths (published by Australian Graduate School of Management – Centre for Corporate Change, University of New South Wales, 1994). For a copy of my model, please contact me: rory_manchee@yahoo.com.au)

1. Fit for Purpose

Various skill sets are needed along the journey from ideation to production, and management has to harness appropriate resources to increase the potential for success. Organisations may need to consider restructuring to maximise their ability to develop sustainable product development systems that incorporate continuous improvement, feedback loops and market responsiveness.

For example, moving from annual software updates to quarterly releases might simply suggest some production rescheduling, but it may also mean changes to documenting user requirements, customer billing systems and client support tools.

2. Playing to Our Strengths

The person who is great at capturing the design specs may not be the best person to undertake market testing with beta users. And it’s generally accepted that someone who is adept at working in a production or QA role on an established product may need some re-training before they get to work on building a prototype.

3. The Model Approach

In conclusion, my analysis reveals that at each stage in the Product Development Cycle, there is a need to review the relevant Business Challenges, address the corresponding Change Issues, and apply appropriate Change Management models or techniques.

 

Update on Perspective – Introducing the “We R One World  Game”

In a recent post on “Perspective”, I commented on the value of stepping back and taking a different look at current ways of doing things. For an immersive, interactive and experiential learning opportunity on how to gain a new perspective on problem solving and how we might address global challenges, the Slow School of Business is running the “We R One World Game” on Saturday, July 25 in Melbourne

Dymaxion_map_ocean2

The Dymaxion or Fuller projection is a world map, which can be rendered in 2-D.

Facilitated by Ron Laurie, and based on the pioneering work of Buckminster Fuller, this event promises to combine a hackathon, a meetup and an unconference all in one! Tickets available here.

Next week: Who needs banks?