My first project:

Hi there,

I have been a big fan of over the years but haven’t had an opportunity to post anything until now :slight_smile:

I have developed my first bootstrapped product which will be launching in beta in August 2016.

It is a tool for developers to help manage 3rd party css and javascript dependencies. It is straight forward to use and it will save time when creating small prototypes or developing large projects.

I would love your feedback and it would be cool to know if anyone would be interested in using such a service.

Thank you


1 Like

Hi Michael,

as a web developer I really like the idea and signed up for your launch list.

As a business owner I would urge you to take a look at your pricing again. Is it really sustainable to offer a free plan with unlimited sites and unlimited bandwidth? Couldn’t this get expensive real fast? Maybe I am missing something here :slight_smile: I would suggest reducing this to 1 site and maybe a limited number of pageviews or whatever to reduce the risk of a pretty high hosting bill for free users.

Good luck with the launch!

1 Like

Hi Daniel,

Thank you for the feedback!

I appreciate you signing up for the launch list, I am really excited about getting the product launched and
I hope you will find it as useful as we did during our proof-of-concept trials.

Regarding the pricing, I agree that a free plan with no limitations could lead to high maintenance and support costs, however, I thought this was worth the risk as it lowers the barrier to entry for new customers.

As we are not planning to offer a trial period, I wanted to offer a way for people to come on board and use the app with very few limitations. If people find the app useful then I hope they will see the benefit of migrating over to one of the paid plans.

It is still early days and nothing is set in concrete so the pricing plans could well change before we launch :slight_smile:

Thanks again for the feedback and I am sure we will speak soon.


I don’t fully understand what it does from the site’s wording.
I signed up for the launch to see how it works though!

Thanks for the feedback. I need to expand the content on the website to explain in more detail how ScriptStack works and what the benefits are.

I will work on this over the next week and hopefully get more images and animated gifs to show examples of the app and it’s dashboard.

In the meantime, I think it’s best to explain what the app does with an example scenario:

Workflow without ScriptStack

  • You are a web developer and create prototypes and client projects regularly
  • you utilise similar 3rd party dependencies in each project - e.g. bootstrap, google analytics, jquery, vuejs…
  • In order to add these to your project, you have two options:
  • Find cdn links or manually download each dependency, add them to your file system and include the style and script references to your project
  • or, set up a build tool to help import, build, compile, concatenate and minify you styles and scripts

Workflow with ScriptStack

Whilst the above options are quite feasible and have served developers for many years, I believe this process can be made even more efficient and help save time in the long term. This is how ScriptStack can help:

  • You will create a new stack in our dashboard (either for a specific client/project, or a common stack to be used in general prototypes)
    • a stack is made up of any 3rd party styles or scripts you require.
    • as a basic example, you name the stack ‘PrototypeStack’ and you add bootstrap and jquery.
    • when you save the stack, our automated process will quickly combine and minify the scripts into one CSS and one JS file.
  • In your projects, you can easily add the stack by adding the following two references to your template:
    • for styles:
      <link href="">
    • for scripts:
      <script src=""></script>
    • the stack references are easy to remember as they are composed of your username and the name of the stack followed by a .css or .js.

A key advantage is that ScriptStack manages your dependencies and enables you to edit your stack by adding/removing scripts and having them served directly to your project without changing any of your projects code.

This provides alot of flexibility and allows you to easily upgrade scripts to new versions without spending time downloading, adding to the file system and pushing them out to the project.

The scenario explained above is very basic but hopefully you can see the benefit of using such a service, especially whilst working in teams and on larger long term projects.

I hope this information is useful but don’t hesitate to get in touch if you need more information



1 Like

I’m not a web-developer generally, but I imagine I’d copy and paste the import section from my previous project and be done with it.

Does it worth to pay for and introduce an extra dependency? Isn’t the problem too small?

Also, I’d be considering a risk that a new service like that may be shut down at some point, and all my links (including those already delivered to clients) would stop working all at once.

I would also expect my client to raise a question why the delivered project has an unnecessary dependency. I imagine they’d request to embed the scripts/css into the code or deploy to a content network of their choice.

It is a neat technical solution, but I doubt it has what it takes to become a business.


Thank you for the feedback and raising the valid concerns.

You are right in saying there is a risk that the business could close down, but I think this a risk shared by most new bootstrapped businesses. Until you reach a good level or MRR, a stable product and a loyal customer base, there will always be that risk.

I can only say that I will give the business all my efforts, energy and make the best decisions to help it succeed. This project started off as a ‘scratch my own itch’ project and soon turned into a bootstrapped business after talking with friends in the industry.

It was clear they were experiencing the same frustrations as I was experiencing so I thought it was an ideal time and project to give it a shot and try to build a business out of it.

To address the concern about a customer having their links stop working if the business shuts down:

I don’t think a concern should exist as from day 1 there will be a ‘download stack’ option for offline/local use. If ScriptStack runs into problems and we had to shut down, I wouldn’t just turn everything off overnight. I would give some notice and a bit of lead time so each customer could make alternative arrangements.

You also touched on CDN services - ScriptStack works in a similar way to a cdn as it will be served directly to your project, however, ScriptStack allows you to customise certain scripts (like Google Analytics) and add them to your project with just one css and one javascript reference.

So for example, if we take bootstrap, jquery and google analytics as an example, instead of having to include many css and javascript references like below:

<!-- BOOTSTRAP -->
<!-- Latest compiled and minified CSS -->
<link rel="stylesheet" href="" integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous">

<!-- Optional theme -->
<link rel="stylesheet" href="" integrity="sha384-fLW2N01lMqjakBkx3l/M9EahuwpSfeNvV63J5ezn3uZzapT0u7EYsXMjQV+0En5r" crossorigin="anonymous">

<!-- Latest compiled and minified JavaScript -->
<script src="" integrity="sha384-0mSbJDEHialfmuBBQP6A4Qrprq5OVfW37PRR3j5ELqxss1yVqOtnepnHVP9aJ7xS" crossorigin="anonymous"></script>

<!-- JQUERY -->
<script src=""></script>

<script type="text/javascript">
  var _gaq = _gaq || [];
  _gaq.push(['_setAccount', 'UA-XXXXX-X']);

  (function() {
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);

You can just do this instead (which is much easier to include and convenient to remember without having to consult documentation)

<link href="">

<script src=""></script>

Another benefit is that you can add/remove scripts straight from our dashboard and not have to change lines of code in the project.

I don’t think this solution is for everyone and it doesn’t fit all use-cases, however, I do see value in it and I believe a good number of other people will do.

Thanks again for the feedback, I hope I have addressed most of the concerns you raised.


Why no trial period? A trial period is great for services of this type.

I share @danielherken concern. Freemium is always risky for bootstrapped companies. It attracts people who have no intention to spend money. They will create multiple accounts with different emails to use additional stacks, rather than upgrading. You want to attract people who are willing to pay. People who just sign up because it’s free, will not upgrade.

I would also consider creating your pricing tiers based on page views (or HTTP requests) instead of number of stacks alone. A client with a single website and 1 million visitors/month will gladly give you more money than a client with 20 websites with a few hundred visitors/month.

Look at for inspiration. If they had a freemium plan for 1 website with unlimited page views, I wouldn’t be paying them, since I only have 1 website that makes money; which is the case for a lot of businesses.

I hope this helps!