
Closed
Posted
Paid on delivery
# Msurface — Developer Handoff Brief *Field-to-office self-reporting platform for microsurfacing road construction.* ## 1. What we are building, and why Work on a road site stops the moment a resource runs out — **Material, Manpower, or Machine (the "3 Ms")** — or any other hindrance hits. Today that bad news travels slowly, and a crew loses a shift before the office knows. Msurface makes it travel in real time, captures it cleanly, and resolves or escalates it automatically. Two field-facing capture surfaces feed one shared office layer: 1. **A Telegram bot** field staff use all day to log problems and progress as they happen — and it tries to *resolve or escalate* in the moment, not just record. 2. **A web/mobile end-of-day (EOD) form** for the consolidated daily record: loads laid, materials in/out, closing stock, manpower, machinery. Both write into the **same database with the same semantics**, so the office sees one coherent picture, not two parallel reports. On top sit role-based dashboards for GM, Coordinator, and Director, covering operations, approvals, masters/HR, and external interactions (vendors/purchase). **Three guiding principles for the whole build:** 1. **Prefer dynamic data over hard-coded standards.** If a value lives in the DB (tolerances, mix targets, lead times, rates), read it from there — and give a UI to update it at the right user level. 2. **Things must tie together.** The same fact captured twice (bot + web, or two pages) reconciles to one record, not two independent impacts. 3. **Build for compliance through easy UI.** Correct reporting should be the path of least resistance. ## 2. Microsurfacing context (enough for a developer) A paver lays a thin cold bituminous slurry over a road at a designed mix ratio. Key model concepts: - **Loads** — work is batched into loads (always "loads," never "sections"); a load can split along its run. - **Chainage** — position in metres from a survey origin, written `18+745`. Above ~500 m, warn-and-confirm rather than hard-reject. - **JMF (Job Mix Formula)** — the approved recipe (aggregate/bitumen/cement/water/additives per m²) per site/treatment. The dynamic standard driving expected consumption and stock cover — a versioned DB record, never hard-coded. - **Treatments** — Type 2/3/5, each with its own billing basis, rate, and JMF. ## 3. Architecture - **Backend:** Python/Flask on Railway — one service that is the REST API, the Telegram bot host, and the scheduler for time-based nudges/escalations. - **Database:** Supabase (PostgreSQL) via PostgREST through a custom `/api/data` endpoint. Flask proxies everything; **no client talks to Supabase directly, no keys in the frontend.** - **Frontend:** self-contained static HTML on Netlify (one file per page), inlined CSS + a single `<script>` block; shared `[login to view URL]` for design tokens. - **Bots:** **M. Rosef Singh** (`@MRosefSingh_bot`, field ops) and **Panam Mistry-ji** (maintenance only). - **AI:** Claude API powers bot reasoning, proxied via `/api/ai`. The bot's `save_to_supabase` family is the **canonical save logic**. Any web save must mirror the bot exactly — fields, defaults, derived values. Read the bot first. ## 4. Roles & access - **Site Monitor** (bot + mobile EOD web): daily capture; sees challan numbers only, never invoices. - **Coordinator** (bot + web): validation, corrections, 10-day plans, stock ledger, vendor/master proposals, disputes; owns invoices. - **GM** (web): cross-site oversight, approvals (vendors, manpower, JMF, calibrations, POs), masters/HR. - **Director**: uses the GM workspace in v1; countersigns JMF. Dedicated view deferred. - **Proxy** (Telegram only): **blocked from web by design.** - **Admin**: system admin; only role allowed to `DELETE` via `/api/data`. **Auth:** 8-digit login = first 4 of Telegram ID + 4-digit PIN (SHA-256). First-timers get an inline PIN-confirm step (last-4 preview) before `set_pin`. Sessions are **Supabase-backed** (survive Railway restarts), 7-day expiry, daily cleanup. Token in `localStorage` as `msurface_token`, sent via `X-Session-Token` header (**not** `Authorization: Bearer`). Every page: auth check at boot, validate via `/api/me` before redirect, per-page role gate. ## 5. Vocabulary that must be correct - **Chainage** stored as **integer metres** (`18745`), displayed `[login to view URL]` / `18+745`. - **TAT step labels:** `CO / SI / LS / LE / SO / CI`. - **All times IST** — every display and schedule. Showing UTC is a bug. Use `todayIST()` and `combineTimeToISO(hhmm)` (builds a `+05:30` timestamptz). - **Stock rollup** (bot writes, web matches): `opening = prior closing`; in/out = sum of today's IO rows for that material; `consumed = opening + inward − outward − closing`. - **Vendor resolution:** usable only if `active=true AND approval_status='APPROVED'`. Unmatched name is **blocked** with "ask Coordinator to add to master" — never silently dropped. - **Discretion is a hard requirement:** field users never see upward-reporting or escalation-chain language; the bot addresses the person it's speaking to, not whoever messaged last. ## 6. Current state Schema is deployed and verified (materials and calibration types seeded, RLS in place). **Mockups are design truth and LOCKED** — "wiring" means keep the visual structure, swap static content for dynamic containers (`id="…"`), add one self-contained `<script>` with the standard `msApi`/`msToast`/`msSignOut` helpers, render live data. Never reflow layouts. - **Site Monitor (mobile, 380px) — wired:** login, EOD home (5-tile checklist), DPR loads, inward/outward (photo intent), closing stock (JMF-driven), manpower roll-call, machinery + fuel events, vendor picker. - **GM workspace — wired:** Overview, Masters, Approvals, site-detail tabs (Today, Stock, Resources, Diary). - **Coordinator — mockups present, wiring pending:** 10-day plan, stock ledger, stock summary/reorder, IO validation, DPR row-states. - **Shared:** `[login to view URL]`, `[login to view URL]`, `[login to view URL]`, `_redirects`, a pending placeholder. - **Bots + full schema dumps** (columns/keys/constraints/indexes/triggers/functions/RLS) **+ paver manuals** in repo. ## 7. Scope to build - **A. Finish Coordinator surface (wire existing mockups):** 10-day plan editor; stock ledger + summary/reorder; IO validation incl. dispute reconciliation (`vws_qty_kg ≠ aws_qty_kg`); pendency list; correction trail (`corrected_by_coordinator=true`). - **B. Complete GM Overview wiring** incl. `events_view` signal feed and `approvals_queue_v` queue. - **C. Build the Admin panel** (only role with DELETE). - **D. Cross-cutting (missing everywhere):** photo/file upload (Supabase Storage; mockups already reserve slots); polling/auto-refresh (today a reload is needed to see bot writes); offline storage/sync queue (field disconnect currently = failed save); notification badges. - **E. Reporting (later, once 2–4 weeks of data):** search, decision-history, exports, Reports tab (TAT trends, calibration drift, productivity, cross-site pace, vendor analytics, JMF cost). - **F. Bot/scheduler:** wire real acknowledgement tracking for adaptive nudge thresholds (gated until ~10k observations). - **G. Deferred:** dedicated Director dashboard (when multiple GMs exist). ## 8. Non-negotiable principles - **Bot/web write parity** — every web save mirrors the bot's save for that record type. Bot is original; web mirrors. Don't change bot semantics for web's convenience. - **Mockups locked** — wire only, never reflow. - **One self-contained file per page**, helpers replicated, **zero credentials in HTML**, all DB/AI proxied through Railway. - **Upsert by natural key for capture** (`on_conflict=<natural_key>`); **PATCH-by-id for in-place edits** (never a new row). `on_conflict` needs a real UNIQUE constraint or errors `42P10`. Unique: `ten_day_plan`, `daily_stock`, `attendance`. `fuel_log` has **no** unique constraint (multiple fuelings/day are valid). - **Single bulk fetch on load** (`[login to view URL]`), render from in-memory state. - **IST everywhere.** - **Toasts must reflect reality** — if no notification is sent, the toast must not claim one. Fabricated feedback is a correctness bug. - **Trace bugs to root cause** — no symptom-patching. **Schema realities:** no `dpr_subloads` table (each sub-load is a `dpr` row keyed `(load_number, section_number)`; UI groups by `(load_number, asset_id)`). No generic `approvals` table — `approvals_queue_v` is a UNION view over 5 sources; query sources directly. `/api/data` DELETE is Admin-only (JMF drafts are commit-once; Site Monitor manpower adds need Coordinator mediation). Triggers can't see Flask session (`SET LOCAL app.current_user_id` is invisible via PostgREST) — identity-dependent logic runs in Flask. Don't let the server broaden a specific `site_id=eq.N` filter to `in.(allowed)` — it silently breaks single-site views. Audit columns/statuses differ per approvable table (e.g. JMF has no REJECTED) — check dumps. **Quality gate before delivering any HTML:** (1) extract inline `<script>` blocks, run Node `--check`; (2) tag-balance count for `html/head/body/script/style/div/button`. Every time. ## 9. Locked decisions (don't reopen for v1) Director uses GM workspace. JMF v1: GM submits + approves with Director countersign (Coordinator JMF → v2). Tolerances use schema defaults. Edits PATCH in place. Mockups locked. Fuel Y→N blocked if events exist. Machinery start-hours are user-logged each shift (equipment runs overnight). Fitters = Mechanic (regex `operator|driver|mechanic`). Site Monitors see challan only; invoices are Coordinator's. ## 10. First steps for the incoming developer (1) Read the field bot end to end; map its save functions to record types. (2) Read the schema dumps for tables you'll touch. (3) Wire one Coordinator page (mirroring its bot save) before the cross-cutting work (photos, polling, offline) that touches every page.
Project ID: 40486265
51 proposals
Remote project
Active 6 days ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
51 freelancers are bidding on average ₹56,316 INR for this job

This looks like a great fit, I will wire the Coordinator surfaces — 10-day plan editor, stock ledger, IO validation with dispute reconciliation — then complete the GM Overview event feed and approvals queue, build the Admin panel, and layer in the cross-cutting pieces: photo uploads via Supabase Storage, polling for live bot-write visibility, and offline sync queuing. My first move will be tracing the bot's `save_to_supabase` functions to map every field, default, and derived value per record type — then replicating that logic exactly in each web `<script>` block so upserts hit the same natural keys and never create parallel records. Questions: 1) For offline sync, should queued writes replay silently on reconnect or prompt the user to confirm before flushing? Send me a message and we can go over the details. Best regards, Kamran
₹43,056 INR in 13 days
8.3
8.3

Hello, your "Msurface: Real-time Reporting Platform Development" project is right in my wheelhouse. I develop modern JavaScript apps end to end — React/Vue/Next on the front and Node/Express on the back, in TypeScript where it helps. Working with javascript, python, website design, debugging, postgresql, full stack development, flask, web api, telegram api, I focus on responsive, fast UIs, clean component structure, and reliable APIs — no page-builder shortcuts. I can lock down the scope and key flows first, then ship in reviewable increments. Can we hop on a quick chat to align on your requirements? ⭐ 5.0/5 from a recent client: "Excellent work by the developer! They built my Video Trimmer website exactly as I wanted. The website is fast, user-friendly, and works smoothly. Communication was clear throughout the project, and…" Final timeline and cost will be confirmed in chat after a complete understanding and documentation of the project expectations in detail.
₹60,000 INR in 11 days
7.4
7.4

As a seasoned full-stack developer, I have accumulated over a decade of experience, especially in Python and Flask technologies. Your project, Msurface, aligns perfectly with my skill set. My expertise in back-end development will allow me to leverage Python's potential to create a powerful and user-friendly REST API service - just as you require. The unified database approach you emphasize resonates with my philosophy of data integrity and consistency to create a coherent user-centric product . One of the central tenets of our company's mission is creating solutions that satisfy our clients while focusing on long-term business relationships. Hence I always prioritize building dynamic interfaces that allow easy update and monitoring without sacrificing compliance. This means your team at Msurface can have confident control over critical data points like tolerances, target mixes, and lead times .
₹56,250 INR in 7 days
7.3
7.3

With 8+ years of professional experience, I think I am a great fit for the Msurface project. My tech-stack aligns perfectly with your requirements for Msurface's back-end. Flask has been my primary choice for crafting REST APIs and host Python bots, and I've previously worked with Railway as well. I'm also skilled with PostgreSQL for which you're using Supabase; making sure that no client talks to Supabase directly is a plus point in terms of security. Moreover, as your bot is being powered by Claude API, it's worth mentioning that I'm experienced in working with APIs to integrate third-party tools successfully. Be it Flask or any other framework like Django or Node.js, I believe in building for compliance through an easy UI. Correct reporting should be the path of least resistance just like you've mentioned in the project description. And I always follow a dynamic data approach rather than hard-coded standards, which fits well with your project's principle. Lastly, my experience doesn't stop at back-end development skillset but also extends to front end - something that could come handy while working on static HTML page on Netlify for Msurface. Together, our strengths could build a coherent Field-to-Office self-reporting platform that processes data seamlessly and provides real-time insights to the stakeholders. Given the opportunity I am confident we can build an exceptional Msurface platform together!
₹56,250 INR in 7 days
6.7
6.7

As the developer for SoftwareLinkers, I am confident that my skills and expertise align perfectly with the Msurface project. With extensive experience in Python and Website Design, I have successfully built and deployed scalable digital systems just like the one you need. My specialization in RESTful API development makes me well-suited to integrate the two field-facing capture surfaces you require - the Telegram bot and the web/mobile EOD form into a coherent system. I fully understand and appreciate your guiding principles of preferring dynamic data, ensuring things tie together and building for compliance. These are at the core of my approach as well. I believe in creating systems that are not only efficient but also easy to use, ensuring accurate reporting becomes the path of least resistance. Moreover, my proficiency in using Flask as a REST API backend alongside Railway for hosting and Supabase on PostgreSQL for database management further validate my fitness for your project.
₹72,000 INR in 16 days
6.4
6.4

With the focus of your project being a real-time reporting platform that specializes in the road construction industry, my team and I believe we are the ideal fit for this endeavor. We are extremely experienced in implementing customized web and mobile solutions like Telegram bots, which aligns perfectly with your need for a Field-to-office self-reporting system. Our proficiency in Python (Backend) and Flask (framework), Railway (API host), and Supabase (PostgreSQL) will ensure your platform is reliable, robust, and secure. In line with your guiding principles, we prioritize dynamic data over hard-coded standards and understand that it is essential for your platform to work cohesively, whether it is through different log sources or reconciling multiple data inputs. This is where our expertise lies. Additionally, with our strong knowledge in Odoo ERP implementation and IoT hardware design, we appreciate that the interface for such a platform should always be focused on making compliance easier for the end-users.
₹156,250 INR in 10 days
6.4
6.4

As an experienced full-stack developer, I am confident that I can deliver precisely what your Msurface reporting platform needs. My 100% completion rate testifies to my dedication to completing projects accurately and on time -- a quality that aligns with the essence of your project. Over the years, I have built powerful web applications, AI systems, and trading bots, all of which required similar principles of real-time data capture and standard-driven rules. Moreover, my skills extend beyond just development. I have expertise in using Telegram bots, intimate knowledge of Supabase database management (using PostgREST), and experience with Railway hosting which resonate perfectly with the specified architecture for this project. Notably, your project requires an understanding of microsurfacing road construction, its key concepts, and dynamic model components like JMF (Job Mix Formula). In conclusion, hiring me means entrusting your project to someone who is not only technologically adept but also committed to writing clean and maintainable code -- a focus that promises a reliable system resilient enough to accommodate future needs. Let us transform the road construction work process through fluent communication between the field staff's loggings and the office's timely addressal; let Msurface be that communication medium - guided by our shared principles!
₹56,250 INR in 7 days
5.8
5.8

With a keen eye for innovation, I bring an approach that perfectly aligns with your project’s goal of streamlining communication between the field and office. My expertise in JavaScript and Python, alongside my experience in website design, makes me the right person to build your real-time reporting platform. Working in unison with your guiding principles, I intend to ensure a dynamic data-driven system that not only captures but also resolves or escalates issues promptly. Having worked on a diverse range of projects across industries with international clients, I’ve developed a deep understanding of transforming complex requirements into clean, reliable solutions. In your particular context, this means a holistic understanding of microsurfacing—a paver's work of laying thin cold bituminous slurry. Finally, one immense advantage I bring is an unwavering client-centered focus. Rather than just delivering on technical requirements, I prioritize understanding your business objectives. By doing so, I can develop a product that not only solves your immediate challenges but also presents opportunities for growth.
₹50,000 INR in 5 days
4.8
4.8

As an experienced Full Stack Developer with over 8 years of expertise, I strongly believe I'm the ideal candidate for your Msurface project. My skillset includes solid proficiency in JavaScript, PostgreSQL, and Web API, all of which align perfectly with the architecture and database requirements you have outlined. Moreover, my prior experience with Telegram API will prove beneficial for flawlessly integrating the bot into your road construction reporting system. Throughout my career, delivering robust, efficient solutions within tight deadlines has been my forte. A noteworthy achievement has been developing complex, real-time platforms that successfully brought disparate data sources together into one cohesive whole. This experience directly resonates with your central guiding principles of dynamic data management and ensuring things tie together seamlessly. Additionally, I understand the specific context and nuances of microsurfacing operations. My understanding of key concepts like 'loads,' 'chainage,' and 'JMF' will empower me to streamline your reporting process effectively. Building user-friendly interfaces that prioritize compliance is a second nature to me, so tackling the challenge of easy UI for correct reporting won't be a hitch.
₹75,000 INR in 7 days
4.5
4.5

Hi, I reviewed the Msurface handoff brief carefully. This is not just a normal dashboard job - the main risk is keeping the Telegram bot, web forms, Supabase schema, IST logic, role access, and locked mockups fully consistent without creating duplicate or conflicting records. I can help finish the Coordinator surface, complete GM wiring, build the Admin panel, and handle the cross-cutting items like uploads, polling/auto-refresh, offline sync queue, and notification badges while keeping the current architecture intact. I'd first match the web saves with the bot and schema, wire one Coordinator page as the working pattern, then continue page by page with the correct fetch, render, PATCH/upsert, IST, role checks, and final code checks before adding uploads, polling, offline sync, and badges. I have experience with Python/Flask APIs, PostgreSQL/Supabase-style data layers, role-based dashboards, Telegram bot workflows, static frontend wiring, file upload flows, and operational reporting systems where data accuracy matters more than visual redesign. Best, Daniel
₹56,000 INR in 4 days
4.6
4.6

Hello, I have extensive experience building operational SaaS platforms, workflow automation systems, field reporting applications, and role-based dashboards using Python, Flask, PostgreSQL, Supabase, and modern frontend technologies. Your Msurface platform is particularly interesting due to its unique combination of real-time field reporting, Telegram bot workflows, operational analytics, and strict data consistency requirements. I understand the importance of maintaining bot/web write parity, preserving the existing UI mockups, implementing secure role-based access controls, and ensuring all workflows align with the established business logic and database schema. I can assist with completing the Coordinator workspace, wiring GM dashboards, building the Admin panel, implementing file uploads, offline synchronization, auto-refresh mechanisms, notification systems, and future reporting modules while adhering to your architecture standards and non-negotiable development principles. My focus will be on delivering clean, maintainable code, seamless integration between bot and web workflows, and a scalable platform that supports efficient field-to-office operations with reliable real-time visibility.
₹75,000 INR in 7 days
3.3
3.3

Hi, I can take over the Msurface platform and complete the remaining Coordinator, GM, and Admin surfaces while strictly preserving bot/web parity, locked mockups, role-based security, and the existing Flask + Supabase + Telegram architecture. My approach will prioritize schema-first development, exact replication of bot save semantics, offline synchronization, file uploads, real-time updates, and production-grade validation to ensure a reliable field-to-office reporting system.
₹56,250 INR in 7 days
2.5
2.5

Hi, I can help with finishing the Coordinator workspace so 10-day plans, stock ledger/summary+reorder, and IO validation (with dispute reconciliation) work correctly with correction trails and role-gated behavior. I’ll start by reading the field Telegram bot end-to-end, mapping its save_to_supabase functions per record type, then wiring each locked mockup to mirror bot/web semantics exactly (UPSERT by natural key, PATCH-by-id edits, IST times, real toasts, single bulk fetch). To reduce risk, we’ll wire one page first and run bot-vs-web parity checks against the deployed schema/RLS. Should we start with the 10-day plan editor or the IO validation/dispute flow? What’s your preferred refresh approach today: manual reload or auto polling?
₹37,500 INR in 3 days
1.6
1.6

Hello, If it has to be built from scratch. first I can start documentation of what you explained above and create screen shot to explain how it will work and what will be look and feel. I have 12+ years of IT experience in SEO, web development with C# dot net (with layer, MVC architecture etc.) , PHP, Wordpress, React, Angular js, windows based software, utilities, different type of API integrations etc. As a programmer I have worked on EPRs, web portal, mobile app design development etc. I am looking forward to hearing from you. Thanks Laxmi Narayan
₹45,000 INR in 35 days
1.8
1.8

For Msurface, I'll leverage my expertise in building scalable backend flows, integrating APIs, and ensuring deployment reliability. My primary goal is to create a clean backend structure that can handle real API, deployment, and error-handling conditions. My experience with multi-client ML inference APIs has prepared me to tackle this challenge. For instance, I successfully deployed a multi-client ML inference API with sub-200ms latency and production-grade cloud delivery, showcasing my ability to handle complex integrations and deployment requirements. To deliver Msurface, I'll focus on the following key aspects: implementing a robust backend flow using Python and FastAPI, integrating APIs for seamless communication, and ensuring maintainability through clean code and documentation. I'll also provide environment setup instructions and a detailed README to facilitate future maintenance. Before starting, I'd like to clarify a few details: what is the target deployment environment, and are there any existing API boundaries or services that need to be integrated? Additionally, is this a greenfield project or an existing service that requires hardening?
₹47,642 INR in 7 days
1.0
1.0

Hello, Your project stands out because it already has well-defined architecture, domain rules, and non-negotiable engineering principles. I have experience with Python/Flask backends, PostgreSQL/Supabase, REST APIs, Telegram bot integrations, and debugging complex production workflows. My approach would follow your onboarding requirements exactly: • Read and map the Telegram bot save logic first (bot remains the source of truth) • Review schema dumps, constraints, triggers, and RLS before touching any feature • Implement bot/web write parity for every record type • Wire existing Coordinator mockups without altering layouts • Maintain Railway → Flask → Supabase architecture with zero client-side credentials • Implement polling, offline sync queues, file uploads, and notification badges • Respect natural-key upserts, PATCH-by-id editing, and IST-only date handling • Trace issues to root causes rather than applying temporary fixes I am comfortable working with Flask, PostgreSQL, Telegram APIs, JavaScript, and production-grade debugging. I also understand the importance of preserving locked UI designs and maintaining data consistency across multiple entry points. I can start by wiring a Coordinator page and validating full save parity against the bot before moving into cross-cutting features. Looking forward to discussing the repository and milestones. Best Regards
₹56,250 INR in 7 days
0.5
0.5

Hi, I can fix your Msurface: Real-time Reporting Platform Development I've solved this exact problem many times. Here is what I will do: - Wire the Coordinator mockups to the Flask/Supabase flow with exact bot-save parity. - Build live stock ledger, reorder summary, 10-day plan, and IO validation with clean reconciliation. - Add polling, upload slots, offline queue, and role-safe GM/Admin access with IST timing. 10 days free support after delivery Milestone-based payment Reply "YES" and Best regards, syed ribal
₹75,000 INR in 3 days
0.0
0.0

You have a well-architected platform already running — schema deployed, Site Monitor and GM surfaces wired — and need a developer who can read the bot logic first, then mirror it precisely into the Coordinator and Admin surfaces without drifting from the locked mockups or breaking write parity. At Marin Software I worked on Python-based real-time data pipelines with structured APIs, role-based access, and webhook-driven event flows — the same discipline this project demands. At Poundit I maintained complex multi-role backends where UI actions had to mirror backend save logic exactly, with no silent divergence. I'm comfortable with Flask + Supabase/PostgreSQL, Telegram bot architecture, and static frontend wiring against a proxied API. My first three days: read the field bot end to end, map every save function to its record type, then wire one Coordinator page — stock ledger is my starting pick — before touching cross-cutting work. That gives you a verified pattern before I scale it across the remaining Coordinator surfaces and Admin panel. The 23-hour deadline on this project concerns me for scope this size — I'd want to confirm you're open to a realistic milestone schedule rather than a single delivery, given the depth of what's left in sections A through D. Can we jump on a quick call to walk through current bot coverage and confirm which Coordinator pages are highest priority?
₹50,000 INR in 7 days
0.0
0.0

With my extensive background in Artificial Intelligence and Software Engineering, I am best suited to develop the real-time reporting platform Msurface for your microsurfacing road construction project. I possess comprehensive experience in building full-stack web and mobile applications with scalable frontend and backend architecture, which aligns perfectly with the development requirements of Msurface. Moreover, my expertise in creating machine learning-based analytical platforms and AI-powered voice and chat agents will be highly beneficial in ensuring that your three guiding principles of preferring dynamic data, interconnecting different layers, and building for compliance are met effectively. Additionally, as a former Chief Technology Officer of an AI startup, I’ve honed my skills not only in creating powerful software but also in managing end-to-end technical development. Understanding the importance of efficient database management, I am well-versed in working with PostgreSQL and can ensure all data is handled securely through Supabase via PostgREST. My proficiency in Python/Flask on Railway provides a solid foundation for building the required REST API, hosting the Telegram bot, and implementing the scheduling functionality efficiently.
₹37,500 INR in 7 days
0.0
0.0

This aligns perfectly with my skill set. I understand the need for a clean, professional, user-friendly, and seamless real-time reporting platform for microsurfacing road construction. Our expertise lies in developing integrated systems like Msurface. While I am new to Freelancer, I have extensive experience in similar projects off-site. I would love to chat more about your project! Regards, Warrick Van Eeden
₹37,500 INR in 7 days
0.0
0.0

New Delhi, India
Payment method verified
Member since Jun 2, 2026
$250-750 AUD
$30-250 USD
$30-250 USD
€12-18 EUR / hour
₹75000-150000 INR
₹37500-75000 INR
£250-750 GBP
$30-250 USD
€18-36 EUR / hour
min $50 USD / hour
$250-750 AUD
$30-250 USD
₹600-1500 INR
£250-750 GBP
₹12500-37500 INR
₹600-1500 INR
₹100-400 INR / hour
₹75000-150000 INR
$10000-20000 USD
₹37500-75000 INR