Project manager/developer (Claude Code)
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted2 hours ago
I’m looking for someone who can wear both hats—project manager and hands-on developer—to drive a new web application from concept to production.
We are looking for a project manager/developer (Claude Code) to lead a short V1: a tablet data-entry app that feeds a database we own, and mirrors the data to our existing Google Sheets.
Context
We import and distributes poultry feed premixes and concentrates. About 80% of sales are wholesale, to around sixty resellers, and 20% retail.
• Points of sale: two retails shops, 5 warehouses. 10 products.
• Management: the owner runs the business remotely from Montréal.
Today, all data lives in one large Google Sheets file. It has become slow and fragile, and anyone with access can change it without a trace. For remote management, this is the core problem: we cannot trust the numbers.
V1 objective
Replace data entry. Staff record every transaction on an Android tablet in the shop. The reports and formulas in Google Sheets keep working unchanged.
The V1 covers entry of:
• Sales to retail customers and resellers, with multiple products per sale;
• Stock movements: container receipts, transfers between sites, returns, damage;
• Daily/Weekly cash closing, with a cash count;
We have an interactive prototype already shows the expected logic (point of sale, cash closing, deposits, weekly report) from Claude. It serves as a visual specification/inspiration.
Rollout starts with a pilot in a single shop, before extending to the other sites.
Target architecture
The tablets (POS) write to a database (PostgreSQL or equivalent), which is the source of truth. It automatically mirrors the data to Google Sheets, in the same structure as today, so existing reports keep working. Any change made in the copy is overwritten at the next sync.
Requirements
1. Offline. The tablet keeps selling without internet or grid power, and syncs when the connection returns, with no data loss and no duplicates.
2. Nothing is deleted. A transaction can be cancelled, never deleted. Every cancellation or correction records the author, date and reason.
3. Price list and resellers. Provided by administration. Any change is restricted to administration, or capped and justified.
4. Credit limits. A credit sale is blocked once the reseller's credit limit is reached.
5. Owner control. Hosting, database, code and domain accounts in the company's name from day one, administered from Montréal. No one in Côte d'Ivoire has admin access.
6. French-language interface, usable by non-technical staff.
7. Maintainable with Claude Code. Mainstream stack, a CLAUDE.md file, documentation and tests, so the owner can evolve the system with the help of an AI coding tool.
8. Backups: automatic daily backups, plus an independent copy, and full data export at any time.
How we will work
The code will be written largely with Claude Code. We are not looking for a full development team, but for an experienced person who ensures the result is reliable and delivered.
The expected role:
• Scope the V1 from the prototype and the current Google Sheets, and break it into deliverable milestones;
• Validate the architecture, especially offline sync and the data model;
• Review and test the code before each release to production;
• Set up hosting (to be discuss and optional), access and backups, on accounts in our name;
• Prepare the field: hardware list and a written installation procedure, to be followed by a local technician without admin access;
• Support the pilot in one shop, then hand over: documentation, training and handover.
Payment by milestones, with the final payment after a successful pilot.
Out of scope for V1
No local tax or statutory accounting: the system is ONLY for the owner's management.
No rebuild of reports: they stay in Google Sheets for now. No PDF invoicing or advanced admin module.
These will come in V2, migrating reports one by one into the app.
Questions for a first conversation
• Have you delivered an offline app with sync before? How do you handle conflicts? 99% of transaction will be online.
• How do you verify AI-generated code before releasing it to production?
• What architecture would you propose for the database and the mirror to Google Sheets?
• How would you break the V1 into milestones, with what timeline and budget range?
• What availability after delivery, and at what monthly cost?
• Do you have experience in West Africa, or with mobile money?
If you thrive on building while steering the ship and you’re comfortable owning both schedule and code, let’s get started. We are ready now.
From Montreal, Time zone EST. French and English.
We are looking for a project manager/developer (Claude Code) to lead a short V1: a tablet data-entry app that feeds a database we own, and mirrors the data to our existing Google Sheets.
Context
We import and distributes poultry feed premixes and concentrates. About 80% of sales are wholesale, to around sixty resellers, and 20% retail.
• Points of sale: two retails shops, 5 warehouses. 10 products.
• Management: the owner runs the business remotely from Montréal.
Today, all data lives in one large Google Sheets file. It has become slow and fragile, and anyone with access can change it without a trace. For remote management, this is the core problem: we cannot trust the numbers.
V1 objective
Replace data entry. Staff record every transaction on an Android tablet in the shop. The reports and formulas in Google Sheets keep working unchanged.
The V1 covers entry of:
• Sales to retail customers and resellers, with multiple products per sale;
• Stock movements: container receipts, transfers between sites, returns, damage;
• Daily/Weekly cash closing, with a cash count;
We have an interactive prototype already shows the expected logic (point of sale, cash closing, deposits, weekly report) from Claude. It serves as a visual specification/inspiration.
Rollout starts with a pilot in a single shop, before extending to the other sites.
Target architecture
The tablets (POS) write to a database (PostgreSQL or equivalent), which is the source of truth. It automatically mirrors the data to Google Sheets, in the same structure as today, so existing reports keep working. Any change made in the copy is overwritten at the next sync.
Requirements
1. Offline. The tablet keeps selling without internet or grid power, and syncs when the connection returns, with no data loss and no duplicates.
2. Nothing is deleted. A transaction can be cancelled, never deleted. Every cancellation or correction records the author, date and reason.
3. Price list and resellers. Provided by administration. Any change is restricted to administration, or capped and justified.
4. Credit limits. A credit sale is blocked once the reseller's credit limit is reached.
5. Owner control. Hosting, database, code and domain accounts in the company's name from day one, administered from Montréal. No one in Côte d'Ivoire has admin access.
6. French-language interface, usable by non-technical staff.
7. Maintainable with Claude Code. Mainstream stack, a CLAUDE.md file, documentation and tests, so the owner can evolve the system with the help of an AI coding tool.
8. Backups: automatic daily backups, plus an independent copy, and full data export at any time.
How we will work
The code will be written largely with Claude Code. We are not looking for a full development team, but for an experienced person who ensures the result is reliable and delivered.
The expected role:
• Scope the V1 from the prototype and the current Google Sheets, and break it into deliverable milestones;
• Validate the architecture, especially offline sync and the data model;
• Review and test the code before each release to production;
• Set up hosting (to be discuss and optional), access and backups, on accounts in our name;
• Prepare the field: hardware list and a written installation procedure, to be followed by a local technician without admin access;
• Support the pilot in one shop, then hand over: documentation, training and handover.
Payment by milestones, with the final payment after a successful pilot.
Out of scope for V1
No local tax or statutory accounting: the system is ONLY for the owner's management.
No rebuild of reports: they stay in Google Sheets for now. No PDF invoicing or advanced admin module.
These will come in V2, migrating reports one by one into the app.
Questions for a first conversation
• Have you delivered an offline app with sync before? How do you handle conflicts? 99% of transaction will be online.
• How do you verify AI-generated code before releasing it to production?
• What architecture would you propose for the database and the mirror to Google Sheets?
• How would you break the V1 into milestones, with what timeline and budget range?
• What availability after delivery, and at what monthly cost?
• Do you have experience in West Africa, or with mobile money?
If you thrive on building while steering the ship and you’re comfortable owning both schedule and code, let’s get started. We are ready now.
From Montreal, Time zone EST. French and English.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.