In the first quarter of 2017, the AppStore and Playstore saw record revenues yet again with a whopping total of $15 billion worldwide, representing a year over year growth of 45%.

Add in other online sales and the amount of money being spent is astronomical.

But how do we process all these sales? And what means of processing is best for your company?

We’ve pondered the question at Process Street and decided to write up our findings. In this article, we’ll compare Stripe, Paypal, Square, and Braintree to see what each do and how they do it. We’ll analyze those findings and suggest which might be better for different kinds of businesses.

The key areas we’ll compare are:

• Features – what do they offer and what can’t they do?
• Pricing – where can we find those small gains which make a difference at scale?
• Ease of use – can a regular person integrate it into their business, or is a developer needed?

But first, let’s look at some of the different use cases for these payment platforms to contextualize our investigation.

Continue Reading

Websites are delicate, messy, and hard to manage effectively. Setup might be easy, but a beginner learning to maintain a website will hit a damaging snag sooner or later.

The main problem is that the tech behind any website is complex for beginners. The files that run your site are written in multiple different languages, depend on each other’s fixed locations, and are controlled by config files. In short, there’s a lot to grasp when you’re starting up a website.

To avoid making mistakes you need a basic knowledge of SQL, cPanel, and phpmyadmin, as well as a general idea of why and how websites work. Like I learned the hard way, tiny tweaks or careless uploads can take the entire site offline for days at a time, which is especially damaging when you have a recurring audience of any kind.

In this post, I’m going to go through the methods you’ll need when maintaining a website, and give you processes you can follow for each task.

Continue Reading

Imagine if you had to send marketing emails manually, or keep your records in a tattered binder on your desk.

Every company, even startups, needs to make a minimum investment in SaaS tools for work like email marketing, project management, and tracking sales.

But the catch is that some of these startup tools can cost huge amounts of money, and when you’re a young startup you don’t want to be forking out in excess of $2,000/user/month for just one piece of software.

The point of this post is to explain the minimum viable SaaS stack your startup should invest in, based on what we’ve found out at Process Street in our many (many, many, many) tool-testing escapades. I’ll even do the math for you, and collate the estimated annual cost at the end.

Ready to start building up your toolbox with the best SaaS out there?

Continue Reading

Today is the first post in a new series – a guide to help consultants and their clients work with Process Street to boost efficiency and be more productive.

Whether you’re documenting your clients’ business processes, updating their toolkit, or generally improving company tools and practices, Process Street is the easiest way to document and manage both your personal and clients’ workflows.

Over the next seven weeks we’ll go through:

• An introduction to Process Street for consultants – why you should care, and the core features
• Advanced features such as process automation and custom share links
• Common use cases and how best to use Process Street in different forms of consulting
• The benefits of Process Street as part of your (and your clients’) toolkit
• How to easily set up and hand off processes to your clients
• How our partner program works
• Extra resources to become a true master of efficiency

I’ll even be writing this guide to let you give it to your clients to teach them how to use Process Street. After all, efficiency is the name of the game.

So, join me today as we kick off this mega guide for consultants by explaining what Process Street is, what the core features are, and why the hell you should care about it.
Continue Reading

Aside from the raw product you’re selling, company culture is everything.

It’s made up of your work environment, ethics, mission, expectations, and goals. You can have a great product, but without a solid culture to back it up, its development can fall apart.

Buffer, for example, has a notable culture of transparency. All employee salaries are published for co-workers and the public to see. They emphasize working out loud and being receptive to one another.

On the other hand, Amazon is noted for its toxic culture that exhausts employees and holds “unreasonably high” expectations.

Which side of the spectrum are you on?

In software companies, it’s important to promote a culture of communication and transparency. What would an issue tracking system look like for a company with poor culture? Pretty desolate.

In this article, I’m going to give examples of how different software companies bolster their QA efforts with a strong culture, and why that’s so important.

Continue Reading

There’s a big difference between successful software companies and those shoddy unverified apps you get off the app store:

Quality assurance.

While small-time apps aren’t heavily used, and the creator won’t receive many complaints or bad press if anything breaks, Google and Facebook are used by billions of people worldwide.

If a bug affects 0.01% of the user base in a small app, it’s not worth the energy. If it affects 0.01% for Google and Facebook, that’s thousands of complaints, and possible media scandal to deal with. And we all know what the price of that can be.

So, when it comes to studying quality assurance there’s no better examples than two of the biggest Internet companies in the world.

I’ve deliberately not chosen to give Microsoft the time of day in this post, because I’d say their QA is pretty damn weak for their size.

…However, read on to pick up tips from Facebook and Google on how to make software that doesn’t break down, cost you more money, and cause frustration for your customers.

Continue Reading

Thinking the terms ‘quality control’ and ‘quality assurance’ can be used interchangeably is a common mistake.

Whoever coined those terms did nothing to clarify their differences, but in fact:

• Quality control (QC) makes sure that your product isn’t riddled with bugs.
• Quality assurance (QA) makes sure engineers are following processes to reduce future bugs, and write code more efficiently.

Quality control is something development teams do every day. They squash bugs in the code they wrote, and run tests to catch future errors.

Quality assurance is the overall management of development processes that make sure less testing and QC needs to be done.

At Process Street, we’ve already looked at the wider implications of QC and how to run tests on your software. We’ve even provided you with a bunch of pre-made software development processes you can adjust to your own team.

In this article, I’ll go into an explanation of quality assurance in software teams, and how you can use this information for your own developers.

Continue Reading

If you’ve been reading our content about the importance of processes, you know the kinds of things that happen when standard procedure isn’t followed. Satellites crash, nuclear reactors melt down, and information security disasters ruin huge corporations.

For software companies, failure doesn’t always have such wide implications but it can mean carelessly shipping a product that creates catastrophic problems for your customers and destroys their trust in you. And of course, it’s a pain in the arse for your development team to fix.

In this article, I’m going to go over some famous software disasters where Quality Control dropped the ball, and look over some common quality control methods.

Continue Reading

In this episode of the Business Systems Explored podcast we talk to Tom Cagely, the host of SPaMcast and Agile expert, about Agile software development. 

When it comes to agile software development, it can be hard to get a comprehensive place to start. Thankfully, this week we speak to Agile veteran and host of SPaMcast, Tom Cagley. Tom goes through the whole Agile process, from tools to best practices. He explains it simply enough for anyone to understand, but also lets us in on a few advanced techniques that surprised us.

Whether you’re actually managing a software team, or just looking to work more efficiently, Agile is well worth adopting in your business. It was born out of the same movement as the lean startup, so you may be already familiar with it, but there’s always room for improvement. Listen to this podcast to learn more.

Links to listen

• Listen on iTunes (iOS)
• Stitcher (Android)
• Listen on Business Systems Explored website

And remember, if you like the show, please leave us a review and rating.

Click below to subscribe on iTunes:

Continue Reading

Productivity is great. The more productive you are, the quicker you work. The quicker you work, the more you get done. The more you get done, the better you’ll feel about the time you’ve spent and the more important you’ll become to your team or company.

Unfortunately, humans can’t work like machines, and so you’ll need a bit of help from technology to work at your most effective pace. From experience, testing, and research, we here at Process Street have collected the 30 best productivity apps ever created for you to cut through your workload.

Now, I’m not saying that you should use all of them; that would defeat the point of streamlining your workflow and optimizing your day. Instead, these productivity apps are best used by picking one or two from each category.
Continue Reading