Forcompanies.
If you have to decide, or to register a new supplier, this is what a company usually asks. The same goes in a PDF you can forward.
Or email me: ny@yustalabs.com
Who is behind it?
It is what procurement needs to register a supplier.
Yusta Labs is the name I work under: I am Nicolás Yusta, in Buenos Aires.
I write the code of every system, put it into production and look after it afterwards. Whoever answers your email is the person who builds it.
- Trade name
- Yusta Labs
- Responsible
- Nicolás Yusta
- Where
- Buenos Aires, Argentina
- In production
- Five client systems (SLE Mensajería, MATIAL, Oro Gym, Daily-installment lender and Cereales y Snack’s Dany) and my own, which runs Yusta Labs.See the work
- Tax details
- The Argentine tax ID (CUIT), VAT status and invoice type come with the proposal, for supplier registration.
- Contact
- ny@yustalabs.com · +54 9 11 2469-3394
What gets signed?
The full conditions are in theTerms.
Before I write a line of code, we sign a proposal with a fixed price.
The scope goes in an annex: what is in, what is out, and the dates for the demo, the adjustments and the handover. Anything that comes up later and is not in the annex is quoted separately, before it is done.
- Payments
- Half on signing and half on handover. There is no subscription and no per-user fee.
- Ownership
- The code is yours from the final payment, by contract (Terms, section 6).
- Confidentiality
- What you show me to do the work stays there unless you allow it in writing (section 8). If your company has its own NDA, I sign it before I see anything.
- Warranty
- After handover, 30 to 90 days of adjustments at no charge depending on the tier: bugs and small changes (section 7).
- Delays
- If a deadline is missed through my fault, compensation is agreed (section 5). If something is missing on your side, the schedule moves.
- Cancellation
- If you cancel before handover, the initial half is not refunded. If it is because I failed to deliver, I refund the part of the work I did not deliver (section 9).
Where does the data live?
I read it from the code of each system on 5 November.
Every system keeps its data in Firestore, Google’s database, on servers in São Paulo.
My clients’ systems share one Google project and each one lives in its own space. The database rules run on Google’s servers, not in the browser: without permission nothing is read or written, and a user of one system cannot see another’s data.
- Who gets in
- Each person with their own Google account, and nobody gets in unless you allowed it.
- What each person can do
- Each person has a profile (owner, office, counter, workshop), and what the profile does not allow is stopped by the database, not just the screen.
- Backups
- The database keeps every minute of the last seven days, and Google takes a daily copy that it keeps for two weeks. Twice a week I take a full copy and store it outside Google.
- Deletion
- The database is protected so nobody can delete it whole by accident.
- The code
- One private repository per system, on GitHub, with two-factor authentication on the account. A change reaches a client’s system only through a separate review (a pull request) and with my approval.
- Certifications
- I do not have ISO 27001 or SOC 2. What this page says is what there is, and it can be checked.
| System | Log of who changed what | Without internet |
|---|---|---|
| SLE Mensajería | Yes: every addition, change and deletion is logged, with who made it, and that log cannot be deleted. | Keeps working and uploads when the connection is back. |
| Daily-installment lender | Yes, the same as SLE. | Keeps working, with a no-signal notice, and uploads when it is back. |
| MATIAL | Yes, the same as SLE, and only the owner can read it. | Everything can be viewed; creating or saving waits for the connection. |
| Oro Gym | Partly: each member has a history of sign-ups and payments, but there is no general change log. | Keeps working, with a notice, and uploads when it is back. |
What if I am not around one day?
This is what happens to your system if we stop working together, for whatever reason.
The code is yours from the final payment, by contract.
If one day you want to carry on with another developer, I hand over the repository, the database and the domain, documented, without you having to ask anyone for permission. While maintenance lasts, I run them.
Every system has its written technical sheet: how it is built, where each piece of data lives and how it is published. That is what the next developer gets.
What is support like?
Both plans, with their price, are onPricing.
With a plan, you write to me by email or WhatsApp and I answer the same day.
A monitor opens each system from outside several times a day. If it does not open, it tries again half a minute later, and if it is still down I get an email right then: the idea is that I find out before you do.
- On-call
- I answer the same day, and if something breaks, I fix it at no charge.
- On-call + Improvements
- On-call, plus up to two small improvements a month and a report at the end of the month. Your messages go first.
- No plan
- The system keeps running the same. If something breaks or you want a change, I give you the price before doing it.
How is it invoiced?
All prices are onPricing.
Prices are published in US dollars. In Argentina they are invoiced in pesos at the MEP dollar rate of the payment day (Terms, section 4).
The CUIT, VAT status and invoice type come with the proposal.
A system or a website is paid once: half on signing and half on handover. Maintenance is month to month, with no lock-in.
Tell me whatyour company needs
I answer by email within the business day.
Or straight to ny@yustalabs.com
WhatsApp: +54 9 11 2469-3394
A 30-minute call is arranged by either of the two.
How a project goes, stage by stage, is in How we work.