- Solutions
- Product
- Resources
- Pricing
- •••SolutionsProduct
- Log in
- Try Fibery ⚡
- Log inTry Fibery ⚡
Startup backstage is an interesting thing to observe. I’ll try to write regular posts about our progress and results. If you read about Fibery for the first time, check this overview:
I think it is better to have some very brief and candid block in all posts to see progress, here is the first try:
Product: Fibery — SaaS B2B (SMB) work management platform
Stage: Alpha (no production version)
Launch: October (silent, invite-only)
Development: 18 months
Cold leads: 520 (subscribed from fibery.io web site)
Hot Leads: 7 (gave feedback)
Customers: 1 (we use it inside our own company, haha)
Team size: 9 people
Burn rate: ~$50K/month
MRR: $0
Feel free to add comments if you think something interesting should be added into this block.
First, some context. We are going to launch Fibery in silent mode in October. The goals of the release are:
It is always hard to define the scope of the initial semi-public release. We decided to focus on core idea (flexible domain) and some visualizations to work with data:
We did several demos to potential customers and started to accumulate initial feedback. To track all this information, I’ve setup basic CRM app inside Fibery. Here is it.
Overall feedback was positive. This one really nails current Fibery stage:
It looks like something fresh on a market. Good design, modern and lightweight. Looks like a product for geeks so far (Templates are important and it is required to HEAVILY invest into getting started). Very good start.
Indeed we paid zero attention to getting started, so it all looks very flexible, but not easy to jump into. We should think deeply about getting started experience with some Templates, Solutions or Bundles.
Vizydrop is a software we create to build charts and reports. Single developer spent 6 weeks integrating it with Fibery and now it is almost ready. It is possible to build reports for any entities you have in Fibery:
We consider Wiki as a very important app in Fibery. People love to start with Documents and later get to work.
In August we’ve added a possibility to upload Images and converted Wiki to a Rich Edit field. It means that you can insert collaborative field into ANY entity. Here is an example how we collaborate on Feature specification:
Quite often people write specifications in separate documents since it impossible to collaborate on Feature or User Story. In Fibery there is no need to have this separation. You can have collaborative editing inside every entity.
In the first release Board will be the only option to work with information, so it should be good. In August we’ve added drag and drop capabilities:
We are not going to invest heavily into Board UI till the release, since we need real feedback to do that. So far it looks like good enough.
We did less than planned (as always). The most risky thing is Collaboration epic (in-app notifications, mentions, sharing views, etc). We did not start this Epic so far, but October is not far away.
Product is taking shape and we see more and more opportunities. It can be applied to various domains and people get excited when see the potential.
Main risks I envision right now:
To be continued → #2. Slow September 2018.
🥊 Startups are struggling. 🇵🇱 +1 Developer. 🇵🇱 +1 Designer. 🇭🇺 +1 Writer. 👓 Content marketing. 💸 Financial management. 👩🔬 Home page experiments. 🏋️♀️ 6 product themes are in progress. 🥹 Per-entity permissions are close...
One of the fundamental requirements of financial operations is to ensure that you have all your paperwork in order. In this article, we will explain why Fibery is a great addition to any accounting software and how to set up an accurate process for managing financial docs in Fibery.
Fibery is an all-in-one task and knowledge management tool for product companies, and when we say all-in-one, we mean it. We run all our operations, including financial ones, in Fibery. Before any tool there is a process, often not an obvious one.
This post offers a comprehensive analysis of the root cause of the downtime and provides actionable steps to prevent similar incidents in the future. It aims to openly address our failure and assist other companies in learning from our experience. We also owe our customers an explanation.