{"id":16556,"date":"2024-07-08T12:36:10","date_gmt":"2024-07-08T09:36:10","guid":{"rendered":"https:\/\/railsware.com\/handbook\/?p=16556"},"modified":"2024-08-30T17:08:58","modified_gmt":"2024-08-30T14:08:58","slug":"how-it-all-started","status":"publish","type":"post","link":"https:\/\/railsware.com\/handbook\/how-it-all-started\/","title":{"rendered":"How It All Started"},"content":{"rendered":"\n
\n
\n
\n

I had a dream – to create a place where happy, talented people work in unison, craft quality products, and do things that matter.<\/p>\n <\/div>\n

\n \"\"
\n

\n Yaroslav Lazor <\/p>\n \n

\n CEO at Railsware <\/p>\n \n <\/div>\n <\/div>\n<\/section><\/blockquote>\n\n\n\n

Today Railsware is a remote-friendly team with three offices and remarkable professionals spread over 28+ countries.<\/p>\n\n\n\n

A big dream and people who share the same values led us to what Railsware is now \u2013 the team with outstanding product expertise acknowledged by clients and millions of users. We grew into a Product Studio that successfully combines two business directions: the development of own products and consultancy. These directions are integrally connected and complement each other. Due to well-functioning product management, engineering, design processes, and polished approaches, we turn ideas into growing products. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The Start<\/h2>\n\n\n\n

The Railsware roots go back to the year 2007, when a small group of tech-savvy enthusiasts established it. One of them later became CEO and plays this role nowadays. That was a long winding road full of experiments and insightful learnings. We worked hard to gain our expertise in business processes and product management. All while continuing to polish our software development approaches. Our first profitable project shaped the product team inside Railsware. That also was a time when our coding culture and delivery approaches evolved.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Product Studio Model<\/h2>\n\n\n\n

Our team always wanted to be involved in the product creation and growth process, not just coding. We practiced different business models and even tried co-founding a few products in the early days. That was a valuable experience, which exposed our business management gaps. The need for new knowledge was evident, and we decided to gain it through learning from successful product companies based in Silicon Valley. We analyzed their cases and approaches in order to apply them to our business. <\/p>\n\n\n\n

In 2012 we met the Pivotal Labs team, and it was a real game-changing experience for us. That knowledge-sharing trip aroused our consciousness and took the Railsware business to a new quality level. We learned about a powerful product discovery tool \u2013 Inception, the advantages of pair work and pair programming, and many other great things, which later boosted the quality of our business processes and product development cycle. <\/p>\n\n\n\n

Powered by this knowledge and a clear vision of how to manage the team, we transformed our team model. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Today, we use the same approaches no matter if we’re working on a client’s product or our own. We invest in our craft and then apply it to building better products. This way, we form a continuous improvement cycle and shape the Product Studio as a platform for successful products’ repeatable creation and growth.<\/p>\n\n\n\n

Railsware Products <\/h2>\n\n\n\n

Experimenting with internal tools laid the foundation for our paid products \u2013 Mailtrap, TitanApps, and Coupler.io. Today, they are used by millions of people around the globe and acknowledged by world-class teams like Atlassian, Adobe, GitHub, Yelp, and Pivotal.<\/p>\n\n\n\n\n \n

\n \n
\n
\n
\n \"\" <\/div>\n\n
\n Mailtrap <\/div>\n <\/div>\n\n
\n

In 2011 while working on a project with our client, we accidentally sent out 200k test emails to the real customers. That was painful but a fateful mistake. We created a solution to never make such mistakes again, without having a goal to earn money on that. The internal tool we crafted appeared to be very helpful, so later we decided to share it with the community. The demand for this product grew and motivated us to turn it into a profitable business. This is how the journey of the Mailtrap began and started our transformation into a Product Studio. Now, Mailtrap is a mature email delivery platform to test, send, and control emails.<\/span><\/p>\n <\/div>\n \n Learn more <\/a> \n <\/div>\n\n <\/section>\n \n \n

\n \n
\n
\n
\n \"\" <\/div>\n\n
\n TitanApps <\/div>\n <\/div>\n\n
\n

In 2017 the Railsware team created a tool for a company-wide transition from Trello to Jira. It was a task organizer built into the Jira application for internal use only. As there was no checklist plugin that had an API on the market, we decided to build one. The same story we had with our first product Mailtrap repeated. We shared our solution with the world, and it turned out to be profitable. With time, it grew into a set of smart tools for productivity, and earned us a status of Atlassian PlatinumMarketplace Partner.<\/span><\/p>\n <\/div>\n \n Learn more <\/a> \n <\/div>\n\n <\/section>\n \n \n

\n \n
\n
\n
\n \"\" <\/div>\n\n
\n Coupler.io <\/div>\n <\/div>\n\n
\n

Railsware is a data-driven team. Documenting, storing, and keeping everything in perfect order is something that we always care about. Our team has done a lot of work importing data into Google Spreadsheets from different data sources, which later resulted in creating a Google Sheets Importer add-on Coupler.io \u2013 our third product that was released in 2020. Later, Coupler.io evolved into a fully-fledged data integration solution. <\/span><\/p>\n <\/div>\n \n Learn more <\/a> \n <\/div>\n\n <\/section>\n \n \n\n\n\n

Culture We Build<\/h2>\n\n\n\n

To leverage the Railsware business, we reinvest profit in our own products and team development. <\/p>\n\n\n\n

From the early days, we made development culture the core of our business. It paid off big time, both with the quality of our projects and Railswarians, who tend to stay with us for 5+ years. The T-shape personality approach unlocks our professional potential in different areas. Through the collaborative way of work, we constantly share our knowledge, learn from each other and master our craft every day. Flexibility and trust are at the core of everything we do.<\/p>\n\n\n\n

Our culture has developed over the long course of Railsware evolution. Now our team stands for a strong belief in the end value of what we do along with continuous learning and improvement.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

We strive to influence the way companies are managed through the proven approaches and the products we build. Our goal is to expand the Railsware formula to the industry, leveraging company reputation and market visibility.<\/p>\n\n\n\n

\n
\n

There is a difference between, \u201cI think\u201d and \u201cI know\u201d. You can build a team only with \u201cI know\u201d. But you can get to \u201cI know\u201d only going through successful experiments and mistakes<\/p>\n <\/div>\n

\n \"\"
\n

\n Yaroslav Lazor <\/p>\n \n

\n CEO at Railsware <\/p>\n \n <\/div>\n <\/div>\n<\/section>","protected":false},"excerpt":{"rendered":"

Today Railsware is a remote-friendly team with three offices and remarkable professionals spread over 28+ countries. A big dream and people who share the same values led us to what Railsware is now \u2013 the team with outstanding product expertise acknowledged by clients and millions of users. We grew into a Product Studio that successfully…<\/p>\n","protected":false},"author":100,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[5],"tags":[],"coauthors":["Olia Ududiak"],"class_list":["post-16556","post","type-post","status-publish","format-standard","hentry","category-management"],"acf":[],"_links":{"self":[{"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/posts\/16556","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/users\/100"}],"replies":[{"embeddable":true,"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/comments?post=16556"}],"version-history":[{"count":62,"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/posts\/16556\/revisions"}],"predecessor-version":[{"id":17146,"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/posts\/16556\/revisions\/17146"}],"wp:attachment":[{"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/media?parent=16556"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/categories?post=16556"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/tags?post=16556"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/railsware.com\/handbook\/wp-json\/wp\/v2\/coauthors?post=16556"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}