Software development FAQ
Find answers about the applications we build, pricing and planning, delivery, technology, ownership, confidentiality, and work after launch.
Services and starting points
What kinds of applications do you build?
We develop minimum viable products (MVPs), web applications, cross-platform mobile applications, desktop applications, integrations, cloud applications, and selected application features that use AI. We also work on performance, release preparation, product improvements based on real use, defect correction, and continued development for existing applications.
Can I start with an existing application or release problem?
Yes. We can continue work on an existing application, prepare a release, investigate a delivery problem, or improve software that is already being used. We begin with the current state of the application and the most important result needed next.
Pricing and planning
How does pricing work?
We divide sufficiently defined technical work into tasks and assign each task a story-point value. A story point is the pricing and planning unit used for technical tasks. At the current rate, each completed and accepted story point is billed at $35.
The project plan lists the current tasks and their story-point values. The planned total produces the current price estimate. Periodic invoices reflect the story points completed and accepted for billing.
How are expected price and delivery timing calculated?
We calculate the price estimate by multiplying the story points in the current project plan by the $35 story-point rate. We use the target delivery pace—the approximate story points planned for each two-week period—to produce a delivery forecast for approximate timing.
The price estimate changes when tasks are added to, removed from, or replaced in the plan. The delivery forecast can also move when the plan or actual average pace changes. The price estimate is not a fixed total-project quote, and the delivery forecast is not a guaranteed completion date.
Am I billed for the target pace?
No. The target pace is the approximate number of story points planned for each two-week period. Story points are the pricing and planning units assigned to technical tasks. The pace supports staffing and the delivery forecast. Periodic invoices reflect story points completed and accepted for billing.
What happens if a period completes less or more work than the target?
The target is an approximate planning pace, not a minimum charge or guaranteed output. The delivery forecast can move when the actual average pace differs from the target. You continue to pay for completed and accepted work.
See the first-version plan, target pace, and approximate timing
Can priorities or planned work change?
Yes. Unfinished tasks can be reordered, removed, deferred, or replaced by agreement. New tasks can also be added. We show the effect on the price estimate and delivery forecast before changed work enters the active plan.
Can a task's story-point value change?
Normally, the value remains unchanged once the task's intended outcome and major requirements are agreed and the task is selected for implementation. A task can contain an internal breakdown of technical steps while keeping one story-point value. Larger or less certain work is usually divided before implementation.
If you request a meaningful change to the outcome or a major requirement, we usually add a new task or replace the unfinished task with a newly planned one with its own story-point value. If the task itself needs to be redefined, we agree its changed definition and story-point value before the changed work proceeds.
Technology and delivery
How do you use AI?
We use AI where it is useful for research, specification, implementation, review, and documentation. An engineer remains responsible for decisions, reviews generated work, and chooses the checks needed for the change.
AI runtime used during development is included in the story-point price and is not billed separately. If your released application uses a paid AI provider, that provider usage is an external operating cost.
What platforms and technologies do you use?
We commonly use JavaScript and TypeScript, React, Next.js, Node.js, React Native, databases, and Amazon Web Services. Depending on the project or an existing system, we can also work with Java, PHP, Python, Angular, and Vue.
Ownership, access, and confidentiality
Who owns the code?
The project-specific code we create and you pay for is yours. Open-source software, third-party components, and pre-existing or general-purpose components remain subject to their existing licences and ownership.
Who controls project accounts and services?
We normally work in source-code repositories and service accounts you control. If we create a new account, resource, or access while doing the work, we make sure you receive the information needed to administer it.
By default, you create and pay for hosting, domains, email, app-store, payment, AI, and other external-provider accounts directly. You remain responsible for reviewing and accepting the provider's pricing. We can help you understand the pricing model and estimate likely usage.
In a special case where using one of our accounts is more practical and may incur substantial provider costs, we agree on the expected cost and how it will be handled before the cost is incurred.
How is the project documented?
Relevant technical documentation is updated alongside the code and configuration so another qualified developer can understand the current system and continue working on it. The exact documentation depends on the application and the work included in the plan.
Can we put an NDA in place before I share confidential details?
Yes. We can arrange a mutual non-disclosure agreement (NDA) before detailed project information is shared. You may send your agreement for review, or we can provide a suitable form.
If you would like an NDA first, mention that in your initial message and leave the confidential information out until the agreement is in place.
After launch and next steps
What happens after launch?
After launch, real users and live operating conditions provide information that was not available earlier. Continued work may include product changes based on feedback or market response, usability and performance improvements, new features, operational improvements, and defect correction.
Post-launch support or continued development is agreed for each engagement; it is not automatically included for a fixed period.
Who do you normally work with?
We work with entrepreneurs, startups, and small businesses that need help making a product decision, building an application, preparing a release, or improving an existing system.
What is the next step?
Tell us what you are planning, what already exists, or where delivery is blocked. The initial conversation is free and helps identify the next useful step.
Still have a question?
Tell us what you are planning, what already exists, or where delivery is blocked. The initial conversation is free.
Send an email