Start a project
To start a project with Nano Soft, email hello@nano-soft.tech with a few lines about what you are building. You hear back from an engineer, not a sales team, within 2 working days.
At a glance
- hello@nano-soft.tech
- Reply
- Within 2 working days
- Based in
- Bucharest, Romania
- Time zone
- EET (UTC+2, UTC+3 in summer)
- Legal name
- Nano-Soft Technology SRL
Your email
What to put in your email
What you are building
One or two sentences on the product and who it is for.
Where it stands today
An idea, a prototype, or a live product with users.
When you need it
A launch date, an event or a funding milestone, if there is one.
A budget range, if you have one
A rough range helps us suggest the right shape of project.
Links: deck, site, repo, designs
Anything that shows us the product or the idea faster.
Next
What happens next
We reply
An engineer reads your email and replies within 2 working days, with questions or times for a call.
- You get
- A reply from the people who would build it
We talk
A call about your product, your users and your constraints. If we are not the right team, we say so.
- You get
- An honest view on fit, scope and risk
You get a plan
We write down the scope, milestones, risks and cost. You decide whether to go ahead.
- You get
- A written plan you can take anywhere
FAQ
Before you write
Will you sign an NDA?
Yes, Nano Soft signs NDAs. If you want one before sharing details, send yours with your first email and we sign it before the call.
Until then, a short description of the product without confidential details is enough for us to tell you whether we are a fit.
Do you take small projects?
Yes, Nano Soft takes small projects when the goal is clear.
A small first project, such as a prototype, a review of an existing app or a discovery sprint, is often the best way to see how we work before a larger build. Tell us the size and timeline in your email and we will say honestly if it fits.
Can you work on an existing codebase?
Yes, Nano Soft can take over or extend an existing codebase.
We start by reading the code, running it and checking how it is deployed, then send you a short written summary of what we found and what we suggest. Only then do we change things, in small steps you can review.