Beta Byte: Who Access



Who Access

Beta Byte is a series underwritten by Bust Out Solutions for that early stage tech found somewhere between idea and traction.


What is the name of the company and/or product? Where is it found online?

It’s called ‘Who Access’ and you can find it at

What problem does this solve and what was the “aha” moment?

Who Access subtly helps companies save money, keep data secure, and empower employees through a simple service request page.

Who Access has a few “aha” moments. After you’re onboarded the moment you see the monthly and yearly costs on the dashboard you get a sense of how important it is to keep an eye on the services your company uses and who uses them.

The next would be when you start getting software requests from users (or make a request) through the request page. It’s very simple tool but you start to feel great knowing you have a straightforward way for employees to request access and for system admins or dev ops to eyes on it.


What is the full launch/release date planned?

A beta version of the site is available now for a 30 day free trial and 20% discount for early adopters. The site has been in development for about a 6 weeks and I’m looking to build the next features based on early customer feedback rather than guessing. So join up!

Who is on the team? 

I’m Cole Erikson, I built Who Access as a side project based on this ‘small’ issue I’ve seen in several companies I’ve worked for. I don’t always tweet but when I do it’s inconsequential.

What is the specific technology or combination of technologies is used?

Who Access was built with Meteor which runs on Node with MongoDB. New features will leverage React.

What is the size/scope of your market and how will you scale?

I haven’t assessed market size. The focus now is product and initial traction. Small growing business between 15 and 80 strong are ideal customers. However, I’ve seen larger with terrible service request systems. I hope Who Access helps them too. : )

I’m not concerned about scaling at this point. I’d love to work with 3-5 Minneapolis/St. Paul based companies and make this product something they rave about.

What is your revenue model?

Annual and monthly recurring subscriptions.

What is your greatest strength?

Solving a specific problem with a small scope.

What is your biggest weakness?

Time. Not enough hours in a day.

What is one resource you could use that would take this to the next level?

A couple great customers.

Is there anything else you would like to add?

The site might be a little slow this first week but other than that give it a try!  I’d love any sort of feedback and let me know when you find any bugs.


Beta Byte: MyLoc

Beta Byte: brodyBall

Beta Byte: Polligo


  • Jeff Pesek

    Hi Cole, thanks for sharing a bit about your new thing. I’ll offer a littlle feedback per your request, take it with a grain of salt, always. This could become a useful forum for open discussion that would help your cause if others reading share in that motive and have thoughts?

    Overall, great problem your addressing, you’ve found a real painpoint to start with! While it’s likely that there already does exist such service(s), definitely a big market with plenty of share to gain. Even better if no one else is doing it. The value prop is pretty clear and well worded.

    Maybe the name/brand could be improved, if you’re not married to it for one reason or another. Then again, great products/services will sell themselves regardless of the name.

    A few exploratory clicks leads me to this blog post of yours: – which I read word for word and enjoyed. I’d encourage you to post that around a bit (r/startups , hackernews, etc) as it evolves. And why not put up on the blog of your product site under about or whatnot? Maybe you have plans to.

    And a few questions, if I may:

    why this tech in particular?
    as a non-technolgist, i love learning more about how developers think and why they make certain decisions. that and im unfamiliar with Meteor + React

    how did you come up with the pricing model?
    the ambition is great! alternatively, have you thought about just focusing exclusivelty on free for X amount of beta users/early adopters to (a) work out any bugs/gather feedback and (b) more precisely measure/determine the value provided? I think the goal of delivering happiness to a few local companies first makes sense.

    • Colton_E

      Jeff, great questions. Thanks for diving in.

      This problem exists and is being addressed by other companies/services. The industry itself is called ITSM (service mgmt) or ITAM (asset mgmt). Big players in the category are services like Samanage & Freshservice.

      While these are great solutions they have a lot of ‘extra stuff’ smaller companies don’t need. And those extras come at a cost most small businesses just aren’t interested in taking on at that point. Kind of a, “Yeah this is a problem for us but not big enough spend $500+ a month to solve.”

      Who Access was built to be simple, straightforward, and do exactly what it claims to do. Do one thing and do it well. I hope to potentially ‘under-do’ the competition. I kind of view them as the Microsoft Project to my Basecamp.

      I definitely have some branding and marketing to get into asap. Admittedly, I’m not strong in the sales and marketing side of things. That is part of the reason I built Who Access. I wanted a project that I knew solved a specific problem and to strengthen my skills in those areas.

      To that point I appreciate your feedback on the blog. It’s definitely going to continue into 2016 and I’ll make sure to post each piece in more social areas. : )

      As far as development goes, Meteor is my framework of choice because I simply have fun building applications with it. It’s a pleasure, pick up projects or start new ones. I started in Rails and Meteor feels as fluid to write in as this sentence. It’s not perfect but few frameworks are. React is being thrown into the project because the ‘Meteor Development Group’ has explicitly stated they will be actively supporting React as a primary way for the view layer to function in their platform. Plus React is pretty awesome so it’s fun to utilize.

      My pricing model is really based on what I would want as a business owner. Full features that cost a bit more based on how big my business is getting. Much like the limited features and design elements of the site, the pricing model is something I’m hoping to refine based on feedback from my customers and the value it’s providing them.

      As a developer I’ve spent months upon months working on other ideas that never got traction. I built great solutions to problems not a ton of people had. Big mistake. Who Access was built in 6 weeks to so I can get it into real customers hands and adjust to fit their needs. Not a fictional version I’ve dreamed up in my apartment.

      To that point, the first tier of the site is free to use then the next does have a prices associated to it after a 30 day free trial. And that price is 20% off what it hopefully will ultimately be. I think it’s important to charge from day 1 for a B2B service. Anyone will take a free candy bar but once you start charging for it you start learning.

      Again, awesome questions Jeff. Thank you. I love thinking about this stuff. : )

      • Jeff Pesek

        cool, thanks for sharing, I love the “underdo” part & hopefully other emerging/aspiring entrepreneurs can learn from your mistakes:

        “As a developer I’ve spent months upon months working on other ideas that never got traction. I built great solutions to problems not a ton of people had. Big mistake. Who Access was built in 6 weeks to so I can get it into real customers hands and adjust to fit their needs. Not a fictional version I’ve dreamed up in my apartment.”