Software Development Plans
We offer predictable software development on monthly plans so you get a fixed number of features delivered at fixed pricing, every 30 days. This innovative pricing model gives you total control of your budget and your feature release schedule.
As a working example of how our development plans work for you, suppose you have 40 software features to get implemented, choosing the Basic plan below, you will know in advance that it will take 10 months to completely finish those features (40/4), you will also know that you’ll be getting a working release every month, and at the monthly budget of $4,500. This is what we call predictability in software delivery!
Up to 1 software feature delivered per month - all layers
Up to 4 software features delivered per month - all layers
Up to 6 software features delivered per month - all layers
Up to 10 software features delivered per month - all layers
Software Architecture documentation
Upgrade Any Time
So what is a software feature anyways?
We have priced our plans around software features. We define a feature as a single software action performed by an actor on an object using one interface. The actor is the entity (human or another system) executing the action, the object is the target of the action, and the interface is the actor’s initial point of interaction such as mobile device, web service, web browser etc… In plain English, this is usually specified in a sentence where the action is the verb, the actor is the subject and the object, well, is the object.
This is simpler than it sounds, so here’s an example. Suppose that you are building an invoicing application for the web where two user roles will be using it: Manager and Bookkeeper. And suppose that you would like a feature where the bookkeeper is able to send an invoice. So here’s how a single feature statement would look like:
The bookkeeper shall be able to send an invoice through a web browser
In the above example “bookkeeper” is the actor, “send” is the action, “invoice” is the object and “web browser” is the interface because it is the point where the actor initiates the action.
On the other hand, if you would like the “Manager” role to also be able to send an invoice, that would count as a second feature because actor has changed. Same thing applies if you would like that same bookkeeper to send an invoice through a mobile app, it would also count as another feature because the interface has changed.
So to summarize, a single feature is an action per an actor per an object per an interface, if any of these four variables changes, then it will count as another feature.