Published at July 10th, 2018 by Izwan Robotys tagged as podcast

Podcast Time!

Its been a while that I've planned to have my own podcast for #notabisnes. Already have some design for it and already discussed with Bukhari Rami for it.

I do not know why it does not start yet. Blame the cosmic karma maybe.

Thus, here just some of the notes to make sure when I revisit this podcast idea again I have everything figured out and can start doing it immediately.

The podcast plan has parts that needed to be laid down first as its foundation. The parts are:

  1. Format
  2. Content
  3. Call to action
  4. Channel

Most of the format that we can see people choose for their podcast was interviews. This is good as interviews will bring external audience and new content to the podcast. This will grow audience based and also keep the content fresh.

So far, I like HBR Ideacast and Neil Patel Marketing Podcast format of interviews. Even if no interview, we can still make it works as long as the content is interesting and structured for bite-sized consumption.

Neil Patel podcast is around 7-9 minutes long. HBR is around 20 minutes long. That would be the range then.

Next is content. As the podcast is about #notabisnes, then the content will be about business too. Will revisit all my previous content to pick out the most engaged one and make it a basis.

Or maybe have a totally new set of content so that it is really fresh. But that will bear more risk as its lack of familiarity towards the current audience.

Or maybe the current audience crave for new fresh content by #notabisnes. I do not know much.

All in all, need to come out with a list of content, a total of 12 episodes with 9 to 15 minutes duration. 12 episode will be a good number for 1 season. The recording will be only in a day and release 12 episode altogether.

This to reflect the 'Netflix Binge Watching' culture. People may like to listen to all the podcast in one sitting to capture its value, and re-listening to it again in commutes as they already familiar the value.

Which bring the CTA: 1) Replay again next time! 2) Subscribe at ! center will list down all available channel, its frequency, topic coverage and how to subscribe.

This will ensure we capture the customer database to be used later. The best part is we can track facebook user that visit the /center to retarget later when we have something to push in front of their face.

The channel was not the biggest concern, as it seems that podcast will be the same wherever channel/platform we choose. The main criterion for choosing channel then will be 1) Audience potential 2) ease of integration.

The first channel will be ... that satisfy both criteria. Marketing will be done via subscription (RSS maybe?) and profile post.

Later will consider uploading the podcast to Spotify and iTunes and SoundCloud.

To summarize:

  1. Format: 9-15 minutes long, 12 episode
  2. Content: Business, Growth, Marketing
  3. CTA: 1) Replay again next time! 2) Subscribe at
  4. Channel: + Facebook post promotion

So much fun!


Published at July 10th, 2018 by Izwan Robotys tagged as podcast

Less Coding More Thinking

In development of a website, front end has become very important as it is the first area where client can see what the developer are thinking. Unfortunately, it is also the most time-sucking area as graphic is much easier to be commented and discussed upon by non-designer, thus creating an unending loop of show design > customer ask for adjustment > show again > more adjustment > repeat till budget gone kaput.

If, by merlins beard the customer has progress beyond that, then comes the challenge of preparing the foundation of the front end code.

These foundation has move further from basic design features such as color, typography, all those subjective 'feeling' that client talk about into more concrete territory such as elements of the website in particular.

Such elements that has become my must-get-it-right-first-before-start-backend are:

  1. Header + Menu
  2. Footer + Menu
  3. Sidebar + Menu
  4. How do error notification shown?
  5. How do success notification shown?
  6. How and what icon sets will be using?
  7. Form inputs
  8. Standard grid: colum based
  9. Standard grid: line based

After confirmed such elements then we move to the bigger picture which are:

  1. Layout 1: Home
  2. Layout 2: Dashboard after login
  3. Layout 3: List Page
  4. Layout 4: Login/register
  5. Layout 5: Object details page
  6. Layout 6: Object details form

What can be considered an Object? Simple: if such 'features' need to have a form, most likely it will involve a database. If it is, then most likely it is an Object. Thus, each object have form and each form need to show details. Hence: each object will got its detail page.

Only after all these was done can we move to more hig fidelity wireframe that will be shown to client once more, and get adjusted one more.

And the cycle repeats untill budget dried up.



Published at July 10th, 2018 by Izwan Robotys tagged as podcast

While brushing up my resume for a career move (hey, its been 4 years with the last startup. Its time to move on), i've gone through a humbling experience of actually understood the flow and value of each stages for web development.

The arrogant me of yesteryear always thought that the actual hands down working on the codes as the most valuable part of a project.

But, the same pattern keep repeating again and again in many of failing web dev projects that make me revisit my current understanding on web development.

And the journey was more than make me realise how fool i am.

Yep, the actual hands on coding part is valuable. But it is not more than other stages of web development.

Each stages and its corresponding expert really do put in values in the project that uptimately see the project towards it completion.

If any of project try to skip any of the stage, then the project will start to suffer from many of the problems that plague failing projects.

So, what are the stages? How do a web development project was done from start to finish? Lets go through the stage one-by-one:

1) Pre-Conception

This is the stage where the client has a bright moment of actualization on the idea of the website. Sadly, it is not the specific website that spark the moment but usually a pain in the market that was discovered by the client.

The pain, and subsequently 'imaginary solution' in the form of a website or an app is what the client usually refer to as 'the idea'.

This is the things that the client does not want it to be stolen from them. As they see that the idea can not be protected by any kind of measure except its obscurity.

The behaviour then introduce the first challenge in web development: to discuss the idea in a comprehensive environment to explore the many possibilities of it.

Only an experienced and trustworthy project manager (or sales engineer) can steer the discussion and having successfully lay down the foundation and the core of the idea. Client (who at the time being was only recorded as prospect) will only discuss their valuable and unprotected ideas with the person they trust or in no-risk environment.

After understand that pain (trust), then we can understand the reason why all these founders (prospect/client) so obsessed with Non-disclosure Aggreement.

2) Conception (User Experience)

3) Design (User Interface)

4) Coding (Front+Back)

5) Test

6) Deployment (System Admin)

So, there you have it, the complete flow of web development:

Pre-Conception > UX > UI > Codes > Test > Deploy

As a developer previously who only concern on the coding stage, it really humbling to at last understand each expert values that they bring in into the project.

Which also make me angry (now) whenever a prospect discounting the budget that has been tabled to their own liking.

A good web development project is when the project was delivered on time and within budget. To do that, the first thing that client-developer need to agree is the value that expected from each other.

If the value expectation does not matched, then it spells disasters clearly and brightly.

Better fire the job, before the job become raging fire. :-D


Published at July 10th, 2018 by Izwan Robotys tagged as podcast

The Reality Of MVP

... Is that it is not about creating something.

It is not about your product.

It is ultimately about your market. Or to be more specific: Market Feedback.

The result of an MVP is not a product, but a lesson.

Said lesson was derived from feedback.

Thus, make MVP to learn from feedback.

Not to fulfill your scope. Or features. Or 'This Sure Gonna Sells' idea.

MVP is nothing without feedback.

Feedback is nothing if you cannot learn from it.


Published at July 10th, 2018 by Izwan Robotys tagged as podcast

Robotys Cheap Website Sources

... that i can offer to my clients is this: RM 870.

Yep. Only RM 870.

With 8 years of experience in web development, handling various kind of project big and micro-small, as a various position (web design, backend, database, digital marketing, scale engineer, sys admin, mobile ui, you name it!), with budget ranging from millions to none (NGO client), that is basicly the cheapest you can get.

And it is not lack of punch too!

Lets see what you will get for that price:

  1. Nice looking design in whatever kind of design the client want.
  2. Properly internally linked web structure to promote SEO and ease of use
  3. Search function to make it easy for visitor to look for information
  4. 1 year small web server capable of handling small-to-medium traffic (up to million visitor a month).
  5. 1 year domain name, if necessary.

How in this world can the price be so low? Well, this are the catches:

  1. No content and copywriting provided. Do it yourself or hire proper copywriter
  2. No photo session or photo editing also graphic design. Hire proper designer for that. Or just D.I.Y. according to standard web design specs. I'll give it to you
  3. Utilizing Web Design templates that can be bought cheaply and easily nowadays. I like themeforest! Ehem: client buy it, not me.
  4. Plain html website OR --->
  5. Wordpress based 'blog/portfolio/catalog' kind of website. No fancy plugins and functionality.
  7. Limited pages, up to 5 'pages'. No worry, that is more than enough actually.

And now we can see why.

This package in a nutshell working on one simple principle:

Only Pay Me To Do Codes

Not to tinker with design.

Not to think the best graphics for the content write 3000 words for the content.

Not to handle photo session and post production for the content (again).

Not to give my codes to third grade system admin that will break the codes (and they blame my codes, not their incompetence).

It seems that there are so many limitation on what this package can do. But wait.

Lets look what is it good for --->

Essentially, this kind of package is perfect for three type of website:

  1. For Online Presence (Company & individual). The first thing people do to verify you nowadays is by looking for you online. Take control of your online presence. Have a representative website.

  2. For Sales Catalog. If you are selling something, might as well have it listed on your own branded website. It will increase your credibility and easier to close a sales. If you are selling service, this can easily modified to be Work Portfolio. It helps prospects decide are your kind of work really suites their needs.

  3. And lastly: For Validation Purposes. The best way to gauge if you can sell something or not is by having an online page for the stuff and drive traffic to it. If people try to order rabidly, then that product/service is a winner! No need to buy stocks or have a shop to validate something.

That is the power of simple & cheap website!

ps: Email me ( if you like to discuss further.