At GetShift we are a technology-agnostic IoT platform that is developing an interoperable, platform agnostic, IoT operating system. We're also having some fun along the way by making devices we need and use internally, including an internet-connected productivity timer, GetTime, as well as internet connected switch, the GetSwtich.

1. If it's not broken, make it better.

2. Creating connections
GetShift creates user-centric IoT
products and the platform to
support them.

3. The team
Experienced UX, Electronics, Web dev, and marketing people sharing a vision.
Sean Greenhalgh
Serial entrepreneur, growth
hacker, electronics guru,
designer, previously CTO of
a startup at Muru-D
Varun Naik Elizabeth Mckenzie
Web developer and hacker,
optimisation and
streamlining expert,
previously CTO at a
connected devices startup
B2B and B2C tech
communications specialist
with client experience from
Microsoft, Google, Capgemini,
SAP, Equinix and Indiegogo

4. By 2019, IoT will add
US$1.7 Trillion to the
world economy.
Hardware alone will account for US $50B,
with the lion's share going to software
makers and infrastructure companies*
*BI Intelligence,http://www.businessinsider.com.au/how-the-internet-of-things-market-will-grow-2014-10

5. By 2021, 1 million
new IoT devices
will be sold every
hour.*
*Gartner report Top Predictions for IT Organizations and Users in 2017 and Beyond

6. The problem
● There are currently several IoT products in the market, each with their own
standard
● They use their own apps and ecosystems to execute commands
● Devices have no knowledge of other products, eg. your light bulbs don’t
know or care about your JBL bluetooth speakers - but this is not the case
for the end-user. Interconnection is key.
● Third party integrations are rarely reliable and require huge improvements.
(Push a button and wait 3-5s to know if your move succeeded). Shaky
integrations with other devices.

7. A new Standard?
But wait, are we trying to create a new
standard? Hasn’t that been done, and
failed because every company comes
up with their own, incompatible with
everyone else, ‘standard’?
How can we address this situation?
With courtesy of XKCD (https://xkcd.com/927/)

8. The solution
The solution is not a new
standard, but to have a
platform that ties together
the APIs and services
provided by IoT devices.
We need to create high
quality, useful IoT devices
to drive adoption of the
platform.

9. We MAKE devices

10. A better customer-centric experience
● The best way to show benefits of a piece of tech is by using it in practice!
● Also a good source of revenue to help keep the base-line running.
● Rapid prototyping to get products out at break-neck speeds.
● Agile development to make hardware less “hard”.
● Continued development of underlying technology while creating our own
products.
● More importantly - drive adoption by improving the customer experience.

11. Where do we fit?
There are already many competing
network infrastructures and IoT
standards being developed.
Telecom networks are fighting over
the next standards in the IoT space.
More and more devices are being
released which people want to be
“smart devices” that you can control
with your phone, over the internet, or
even by other devices.
Networks
IoT Standards
Device Manufacturers

12. Where do we fit?
We create modular parts of the IoT
experience, from prototyping boards,
to simple add-in hardware modules
which can be integrated into existing
designs.
We also create the software (web,
native mobile) to control and integrate
devices into your smart network.
Networks
IoT Standards
Device Manufacturers

13. But can’t big manufacturers just
build it all themselves?

14. NO!
In 2016 one of the largest ddos
attacks on major companies was due
to insecure IoT devices
Ad hoc development has lead to bad
code as inexperienced companies left
huge vulnerabilities in their code
Different mistakes were made by
different companies
Every bit of hardware was different,
and code was different so it was
impossible to update and patch the
security flaws in time

15. How it works
Step 1
Build devices while
developing underlying
technology
simultaneously
Step 2
Create unified IoT
experience throughout
all the devices
Step 3
Licence technology and
IoT hardware and
software modules to
3rd party companies.

16. So what products are we creating?
● Internet connected productivity timer
● Smart home switch and controller device
● Smart bike and transportation tracker
● ….and a platform with the ability to make
much more!

17. How far along are
we?

18. Pretty far!
● <2 months from concept to beta
test product.
● First product has 80% of
technology already developed
for 2nd product
● Rapid prototyping using 3d
printing and outsourced
hardware partners
● Iterative development by using
“development platform” ideals
● We did say breakneck
development speed!

19. Revenue Model (Stage 1)
● Create useful gadgets that will be attract interest on crowdfunding
websites
● Lower risk by taking pre-orders to gauge public interest
● Highly focused market segments with a high number of influencers
● Strategic development of underlying technology while the ability to keep a
steady cash-flow
● Post-crowdfunding sales to keep base-line cash flow through online
channels and/or bricks and mortar retail.
Creating and selling our own devices and
gadgets

20. Revenue Model (Stage 2)
● Licence and provide support for 3rd party companies developing their own
IoT devices
● Allow them to leverage the experience, safety and security of using a
platform that is being maintained and improved
● Compatibility with all other devices which are on the GetShift platform (a
big issue currently with IoT devices)
● Charge support fee and development fee while device is in R&D
● Per device charge model, and monthly ongoing for using GetShift
Licensing GetShift Platform and
Technology

21. Questions?