We all started out as freelancers of some sorts, and starting out may of us found it difficult dealing with clients when it came to delays in payment and funds. They need a system of payment that would work for all client types. That's what we call Spincrow. Our Mission was to develop a better system to handling business finance for freelancers and online retailers and help them excel.
We developed a new product from the ground up, capturing the essence of the idea with relation to enabling faster payments and milestone based delivery of funds for the users (freelancers, retailers, you and me, e.t.c). An highly effective platform managing funds from clients to service personnel, and we developed all product launching requirements for the success of a new platform. From onboarding functionalites to S.E.O.
The platform was set to launch by the 16th of May. We've already gathered more than 300 potential client mail, in the span of 1 week, validating the importance of the problem.
Processed more than 1,500,000 naira worth of transactions within 2 months of product launch.
none at the moment (coming soon)
Tech cabal please feature this.
As creatives we have always had some issues with fund management. sometimes it's with getting it from our clients, other times business priorities might cause infringements when paying us. In order to resolve these problems some individuals choose to draw up contracts which specify the means and structure of payment for work delivered, sometimes these are not followed, so we decided to take things one step further.
We decided to automate payment contracts and make them enforceable digitally. In order to make sure we understand the idea there are quite a few things we have to do better grasp our targets.
First we reached out to a few individuals (other freelancers) to get an idea of what they experience dealing with clients when it came to payment, There are usually 3 major scenarios which comes into play from time to time.
In order to make it clear to ourselves, we needed to learn just a little more, and this required imagination, putting ourselves in the situation of the clients, we came up with a user analysis for our potential user base. This was meant to give us some insight into the user's life a typical day and who they might be using the product for.
Initial designs were almost spot on, we had to first of all come up with the various pages and UI structures these pages would follow, these helped us understand how we are going to take the project to the next step implementing these designs. Onboarding was really a huge portion of the project and we considered it pertinent that our users be able to fully setup completely on the app without being confused about where things went.
Therefore giving rise to the structure
With the structure in place we started designing the UI of these pages. Usually we'd move with a mockup set, We proceeded to start the design process in XD. with a mockup first after which we move ahead to design the actual UI. We usually have several design inspirations from which we draw upon, taking a good look at what as already worked in the past, and looking for new ways to deliver quality.
After our design process, coding / implementation followed almost immediately, Asides design this is usually one of the most painstaking planned processes. Developing the product from the design implied several important aspects to be taking into account.
Based on these touch points we decided to use grapql and node for the backend apis and react for the frontend stack. with respect to graphql, there were many ways to implement the architecture, but we opted for prisma which is essentially an orm for database management via graphql schematics.
usually we started out with the backend grapqhl api then proceed to build the react based frontend. Development of the project was a very intensive process, taking about 5 months.
With development session done, the next step was to review a product launch checklist which is meant to confirm the product's status for launch, with that we were able to ensure the following.
At the moment of writing this, the product is going up for beta testing ( May 16th, 2020). The idea is to have our first collection of potential users test the app and give us some feedback about the their experience using the product. and how it influences their process.