I’ve reviewed the files you sent. Here is what is ready, what I’ll finish, how I’ll look after the site, and what each part will cost. The ordering app is planned separately.
The design, menu, images and animation are already supplied. The project builds successfully. My review found a short list of things to resolve before customers use it.
I’ll remove that block and complete the basic Google setup so the public website can be found.
I’ll connect each location to its correct approved ordering page, or one correct location-choice screen.
Hours and phone numbers are missing. The “15 min” pickup label is fixed text. Prices, review quotes and photos need the owner’s approval before launch.
For this first website, small approved changes go through me. A dashboard for the later ordering app is a separate part of that project.
I’ve checked the files and whether they build. Phone and desktop testing, including the animation, will be completed before launch. There are also builder leftovers to clean up behind the design.
?Tap a gold question mark for an explanation of how that part works for this project. The main scope and costs are written on the page.
You keep the supplied design. I take it through preparation, your review and the public launch.
Clean up the unrelated builder page and unfinished launch settings. Add the approved hours, phone numbers, prices and photos. Correct or remove the fixed pickup-time claim.
Set up the approved Order destinations and check the location/contact links and any included forms. Test navigation and the animation on iPhone Safari, Android and desktop.
You can open the prepared site on your phone, check the wording and details, and request revisions before it replaces the current website.
Set up hosting, connect hangryjaja.com safely, point both existing Google Business listings to the agreed site, complete basic Google setup and complete the launch checks.
The new files do not contain the ordering system currently supplied by Owner. This is the one dependency we need to settle before changing the live address.
They view the new site and tap Order for Grand Prairie or Fort Worth.
The approved ordering service opens and handles checkout.
The restaurant continues using that service’s verified kitchen workflow.
For the first launch: I recommend retaining the current ordering service if Owner can provide a supported working address for it. I’ll verify the links before the website switch.
If Owner is being cancelled at the same time, we need to select and test a replacement before switching. Replacing its ordering, payments and app is outside the website launch scope.
The restaurant keeps its payment account and receives its sales. If Owner continues handling orders, its applicable subscription and payment fees continue too. A new marketing website does not remove those charges.
You keep designing and selling. I handle the website setup, hosting and agreed care.
The supplied files are already set up for Cloudflare. It is a low-cost fit for this website and avoids the work of managing a separate server.
I’ll use our managed Cloudflare account, set up the site and pay the provider. You pay us through Upwork. You do not need a separate hosting account or provider bill for this website.
Send approved small updates through Upwork and I’ll make them within the monthly editing allowance. Larger content jobs and a new editing system are separately quoted.
The text-editing allowance is separate from the included routine checks and upkeep. Unused editing time does not carry forward. Extra content changes, new pages, redesigns, features, ongoing search marketing and app operations are quoted separately.
hangryjaja.com stays in its name. If email uses that address, I preserve those settings before the website change.
You supply the design and approved business details. I handle the agreed technical work and explain any new scope before quoting it.
Care can be cancelled anytime. I hand over the site files, code and launch notes so hosting can move elsewhere. Service continues for the agreed paid period.
The main cost difference is whether we configure an existing ordering service or build a new system the restaurant depends on.
I configure a suitable existing ordering service. Customers use its ordering screen, and the owner uses its existing management screen.
This route needs a provider/account and menu check before I can confirm it. No new provider has been selected.
A limited first version for one selected location: menu choices, cart, secure payment, confirmation, basic owner controls and a browser kitchen screen.
A second location, delivery, loyalty, saved accounts, campaigns or transferring old customer data can change the quote.
For the custom route only. This is an illustration, not a dashboard already included in the supplied website. Tap a screen name to see its proposed controls.
Selected location: pilot location. All records below are examples.
Example controls. Names and prices are placeholders, not an approved restaurant menu.
Example controls. These are not Hangry Jaja’s confirmed business hours.
One selected location for the proposed first custom version.
Detailed payment records and refunds can remain in the payment provider’s own dashboard unless we include those controls separately.
An Apple App Store release is another piece of work. A browser ordering app, even one added to a phone’s home screen, is different from an App Store listing. The app estimates below do not include Apple publication. I’ll quote that work in writing after we choose the ordering route.
The first site establishes the setup. The next sites should arrive with fewer things to fix.
New features, a large catalogue, bulk data entry, custom checkout or ordering, new owner dashboards and repairs to a broken build are separately quoted. I confirm the scope before accepting a standard-rate job or batch.
The building-material supplier’s source and catalogue have not been reviewed under this quote. I won’t treat that as the same scope as this restaurant website.
All prices are in USD. You can commission the website on its own; the later app is not bundled into this launch.
All of the website work listed above: preparation, approved details, location links, hosting setup, phone/desktop checks, the address switch, basic Google setup and handover.
The prepared site for you to review on your phone.
Agreed revisions, the live address and final checks.
Two Upwork milestones.
Once the website is live: hosting, routine checks and upkeep, plus up to 30 minutes of approved minor text updates per site each month. Monthly service, cancel anytime.
You pay us through Upwork. We pay Cloudflare from this fee. There is no separate Cloudflare bill for you under this arrangement.
The fee pays for managing each site as well as hosting it. It is not just the hosting company’s price. Extra features and unusually large hosting needs are agreed separately.
The first site needs the specific cleanup, approved business details, location links, Google settings, phone checks and safe address switch listed above. The $250 covers that complete reviewed launch, rather than publishing ready-made files unchanged.
After this setup is proved, the lowest repeat rate below is available for standard sites in a batch. A thousand-page site, a large catalogue or a new payment workflow would need a separate scope.
| How you commission the work | Launch price per site | Batch total / condition |
|---|---|---|
| One future standard site at a time | $200 | Each scope is reviewed and agreed individually. |
| Five future standard sites together | $150 | $750 total, with the full agreed batch budget funded through Upwork before batch work starts. |
| Ten future standard sites together | $100 | $1,000 total, with the full agreed batch budget funded through Upwork before batch work starts. |
Optional future work: you do not need to buy a batch to start Hangry Jaja. These rates apply after the first launch setup is proved, to sites meeting the standard scope above. The current $250 launch and monthly care are separate; discounts do not stack.
For a batch, we review the files and agree the sites, scope and delivery schedule together before funding. Upwork holds project funds until the agreed work is submitted and approved under its process. Funding is not the same as releasing all payment before delivery.
The care offer is $50 per live website per month. Hosting can share one provider account, but each site still has its own checks, upkeep and changes.
| Live websites | Monthly website care |
|---|---|
| 1 | $50 |
| 5 | $250 |
| 10 | $500 |
| 20 | $1,000 |
| 30 | $1,500 |
These are care totals only. The one-time launch rates are shown above; care stays separate from any batch launch payment.
| Route | One-time work | What that figure means |
|---|---|---|
| Existing ordering service | $300 setup target | Limited setup using a complete approved menu and a supported account. Subject to the provider/workflow check. Extensive menu entry or moving data changes the quote. |
| Custom pickup web app | $1,500 provisional estimate | The limited, one-location version described above. I fix the quote after agreeing menu rules, owner controls and the order workflow. |
| Apple App Store release | Separately quoted | App build, device tests, listing and submission work, scoped after the ordering route is chosen. Not included in either figure above. |
Its subscription, payment-processing charges and any hardware. I’ll check the relevant plan before recommending a provider. Keeping Owner for ordering keeps its applicable fees.
Data storage, any messages/notifications, payment fees and the required support arrangement. These will be itemised before production. The website’s monthly care fee does not include running a custom ordering operation.
Apple’s standard Developer Program membership is currently $99/year, separate from development and submission work. The appropriate account/submission route must be agreed.
The restaurant’s domain renewal remains separate.
For the website decision now: $250 once, then $50 per site per month for managed hosting and care. Domain renewals and the restaurant’s ordering/payment-provider fees are separate. App work needs its own agreed scope.
I can handle the arrangements through Upwork. You do not need another meeting to choose a hosting platform or explain technical settings.
I complete the agreed launch preparation and send the review link. You check the wording, business details and design.
I apply agreed revisions, verify the ordering links, connect the live address, and complete the Google setup.
I handle hosting, the small checks and approved minor changes. The app remains a separate project.
Timing: about 3–4 days after the required access, approved business content and ordering arrangement are ready. Provider/account verification delays can affect the launch date.
If the answer is yes, I’ll verify a supported ordering address before moving the website. If Owner must be replaced at the same time, we need to agree and test that replacement first.
What I need alongside approval: confirmed hours and phone numbers, approved menu prices, review quotes and photos. I’ll arrange domain and Google access during onboarding.
To proceed: confirm the website scope and care arrangement on Upwork, and we can set up the two $125 website milestones.
Five restaurant sites combined into one with location pages: blendrestaurants.com.
Agency backing from Wix Patriots, a Wix Legend Level Partner with 2,000+ websites.
Prepared by Muntaha. Project discussion and payments stay on Upwork.
Yes, provided a working ordering service remains available and its links are verified. The website quote is independent of the app estimates.
The supplied website has no dashboard, and this launch does not build one. Small approved text updates go through me under care. Owner controls for ordering are part of the chosen later app route.
Yes. Care can be cancelled anytime. I hand over the website files, code and launch notes. The domain stays with the restaurant, and a new hosting arrangement is needed after our service ends.
These are the same project explanations available from the gold question marks.
I inspected the supplied website files, the menu and links stored in them, the launch settings and the parts left over from the AI builder. The project also passes its build and deployment packaging checks.
Those checks tell us the files can be prepared for hosting. Checking the actual appearance, animation and links on phones and desktop is still part of delivery before the public launch.
The supplied files contain two instructions telling search engines not to list the website. Those are often useful while a site is unfinished, but they must be changed for a public launch.
I will remove those blocks, check the page title and description, and connect Google’s free website-checking tool. This allows Google to read the site; Google still decides when to list it and where it ranks.
Both locations currently send customers to the same Grand Prairie ordering page. Someone looking at Fort Worth could end up at the wrong ordering destination.
I will use the restaurant’s approved link for each location, or one correct screen where customers choose their location. Both destinations will be checked before launch.
The supplied website has no private editing screen. You or the owner send me the approved text change through Upwork and I update the website files.
Monthly care includes up to 30 minutes of small text updates per site each month, alongside hosting and routine checks. Unused editing time does not carry forward. Larger changes or a new owner editing screen are separately quoted before work starts. A later ordering service may already provide its own editing tools.
The AI builder left an unrelated public app page, builder branding and unfinished launch settings in the project. Those are not part of the restaurant website you want to deliver.
I will disable the unrelated page and replace the unfinished settings, while keeping components the design needs to run. This is preparation of the supplied site, not a proposal to rebuild its design.
I will send you a private review link you can open on your phone. You can check the design, business details, locations and ordering buttons before the new site replaces the current one.
The first milestone is for that prepared preview. The second covers the agreed revisions, the live address switch, the Google setup and handover.
I will remove the search block, check the website title and description, connect Google Search Console and update the website link on both existing Google Business listings with access.
Search Console is Google’s free tool for spotting website search problems. This is basic launch setup. Ongoing content, advertising and work to improve rankings are separate services.
Owner currently supplies more than the public website. It also hosts the ordering page customers use to choose food, pay and send orders into the restaurant’s workflow. That system is not inside the new files.
When hangryjaja.com points to the new website, the old ordering path will not automatically exist there. We need a working ordering address supported by Owner, or a tested replacement, before making the switch. Keeping Owner’s ordering service also keeps its applicable fees.
No new Stripe checkout or point-of-sale connection is included in the $250 website launch. It includes connecting and checking the correct existing ordering links for both locations. Customers continue choosing food and paying in the agreed ordering service.
Stripe is a payment processor. A point-of-sale system is the restaurant’s counter sales system. Taking an online payment does not automatically send a usable order to that system or its printer. Any new connection belongs in the separate ordering/app scope, after compatibility is checked. The restaurant owns its payment account and receives the sales.
I will set up the service that keeps the site online, connect the website address, manage routine website updates and carry out the small checks listed in care. You do not need to operate a server or manage a Cloudflare bill for this website.
You pay us through Upwork. We use our managed Cloudflare account and pay the hosting provider from the care fee. The restaurant keeps its own domain and payment account.
The AI builder has already configured this project for Cloudflare Workers. Cloudflare runs the website and its small behind-the-scenes page program without a separate server computer for us to maintain.
Its paid account starts at $5/month with included usage and can contain several small sites. We pay that provider cost. The $50 per-site care fee also pays for that site’s routine checks, upkeep and limited minor text changes; it is not just Cloudflare’s subscription price. Unusual traffic or processing needs are reviewed before an expanded service is agreed.
The restaurant keeps hangryjaja.com and its payment account. The hosting is managed inside our Cloudflare account. You keep your customer relationship and the design work.
If you leave, we hand over the website files, code and launch notes so they can be hosted elsewhere. Continuing to use the domain does not require keeping us as the developer. A replacement hosting arrangement is needed after our service ends.
A website address and email on that address can use the same domain settings. Moving the website carelessly can therefore affect email, even though the email service is separate.
If email is in use on hangryjaja.com, I will preserve its existing settings before changing the website connection. We can arrange the necessary access during onboarding; you do not need to explain the settings yourself.
The $50 per live website includes its hosting, routine availability/link/form checks, routine software/security upkeep and up to 30 minutes of approved minor text updates each month. The editing allowance is for changes such as hours, a phone number or a price; it is separate from the included routine checks and upkeep.
Unused editing time does not carry forward. Additional changes are quoted first. New pages, redesigns, integrations, ongoing SEO and custom app operations are outside this service. Care is monthly and can be cancelled anytime. I check any unusually large traffic, storage or processing needs with you before agreeing expanded hosting.
Instead of creating a new ordering system, I would configure an existing service that already has an ordering screen, payments, owner controls and supported restaurant connections. The business uses that service’s available branding and features.
This can only be confirmed after checking the restaurant’s account, approved menu, equipment and required workflow. The setup target does not remove the service’s subscription, processing charges or hardware costs. No provider has been selected yet.
The proposed first version is a pickup-ordering web app for one selected location. It includes menu choices, a cart, secure payment, order confirmation, basic owner controls and a browser screen for kitchen staff.
Before fixing the price, we agree item count and options, tax, tips, pickup timing, cancellations and which existing features must remain. Two locations, delivery, loyalty, saved accounts, campaigns and data transfer can change the scope.
A custom app needs to save the order, check its price, take payment and receive the payment company’s direct confirmation. It then marks the saved order paid and presents it to staff. A payment success page alone is not enough.
The first custom version would use a browser kitchen screen. Failed connections need a visible record that can be retried without making duplicate orders. Connecting directly to a point-of-sale system or printer is separate work.
No. The example shows the kind of controls proposed for a later custom app: paid orders, menu/prices, sold-out items, hours and pausing new orders. The records and controls are illustrations only.
The website launch does not include building this dashboard. With an existing ordering service, the owner instead uses that provider’s dashboard, to the extent the chosen plan supports the required controls.
For the limited custom app, detailed payment records and refunds can stay in the payment provider’s own dashboard. The restaurant owns that account.
This avoids rebuilding those controls for the first version. If refund controls are required inside the new app, we include that requirement in the written scope before fixing its price.
A web app runs in the phone’s browser. It may also be added to the home screen. An Apple App Store release needs its own app build, device testing, store listing and Apple review.
Neither app estimate in this proposal includes Apple publication. After choosing the ordering route, I will quote the appropriate store work in writing. Apple’s standard Developer Program membership is currently $99/year, separate from development. Approval and timing are decided by Apple.
The first Hangry Jaja launch is $250 for the reviewed files and the listed preparation: cleanup, missing details, location links, Google settings, phone checks and the safe move to the live address. It is not an open-ended price for any website.
Once the standard setup is proved, the $100 per-site rate is available for ten eligible future sites in one reviewed, funded batch. Future individual standard launches are $200, or $150 each in a batch of five. These rates do not include new checkout, point-of-sale connections, custom apps or large catalogues.
The fixed website offer is split into two Upwork milestones: $125 for the prepared private preview and $125 for the public launch with the agreed checks, Google setup and handover.
Managed website care is $50 per site per month once the site is live. The app is commissioned separately. Sending or reading this proposal does not order any outside service.
Yes. The restaurant’s domain renewal, any ordering-service subscription and transaction fees remain separate. An app may also need paid data or notification services and its own support agreement.
I will identify those costs with the chosen app route before production. The current website does not need a new app database. We are not selecting or activating app subscriptions as part of this launch.
The first launch establishes the hosting setup and checklist. I then give you a short instruction for your AI design tool so future files arrive with the agreed structure, complete assets and approved content.
Future eligible sites can be bought individually or as an agreed, funded batch at the listed rates. Discounts reflect standard preparation and grouped work; they do not make complex sites the same price as simple ones. I review the files first. Extra development is quoted before acceptance, and the original Hangry Jaja launch is not repriced as part of a later batch.
A small public business website: up to five standard content pages, one language and one website address. You supply the complete approved design, text, images and business details. Its files must fit our agreed setup and pass the launch-readiness review.
An existing booking or ordering link can be checked and connected. New features, a large catalogue, bulk data entry, custom payment or ordering flows, owner dashboards and repairs to a broken build are separately quoted. A long or complex page is not automatically simple just because it uses one address. I confirm eligibility before accepting a standard-rate job or batch.
After the first Hangry Jaja launch, a standard future site bought individually is $200. A batch of five eligible future launches is $750 total ($150 each); ten is $1,000 total ($100 each). The first $250 launch and monthly care are separate.
For a batch rate, we review all the files and agree the scope and delivery schedule together, then arrange the full batch budget in Upwork project funds before work starts. Upwork holds funded money until the agreed work is submitted and approved under its process. Funding a batch is different from releasing all payment before delivery. You do not need to buy a batch to start Hangry Jaja.
No matching explanation. Try “orders”, “hosting” or “payment”.
This plan is based on the supplied website files and the meeting discussion. Provider facts were checked for the review dated 8 November 2026. Final app pricing depends on the chosen service and agreed requirements.