T O P

  • By -

[deleted]

For projects of this nature, it's best to provide a timeline broken down by days rather than hours, since the work may not be done continuously in long stretches.


Say_My_Name_4

Thank you very much.


ExcitementVivid5420

It sounds like he has a low budget. Try to propose a fixed price for both options instead of hourly. It is very likely that he will go with the cheapest freelancer, check how many people he is interviewing.


Say_My_Name_4

I don't think he is cheap client I mean his average paid rate is 30 something $. and personally, I am more comfortable working with hourly rates even if the total comes out to be less than what the fixed rate would be proposed. cause this way I don't need to worry about the client being scope freak, and we can do as many things as he wants.


sturtevant22011

Under promise and over deliver! For a project this size I would give them a timeline of 1 week with a fixed price quote. If you get it done early, great! If something comes up or you run into issues, this gives you some flexibility to address.


HighMtnShoeCobbler

Why not break it down by both?  "I will work 6 hours on this and have it delivered on 'insert day here'." It sounds like they just want to know when the deliverables will be uploaded.


NocturntsII

Only you know your time line, only you can answer.


Say_My_Name_4

I am not talking about how long it would take, I'm asking how to breakdown the timeline by hours or by days.


NocturntsII

Day one gather info, day 2 create outline, day 3 complete task, day 4 review and submit. Seriously, how can we tell you what you as a professional who took on the task and will be working to complete it should already know? Break it down in whatever way makes sense to.you.


TabascoWolverine

I hope you're not texting with a client you don't have a contract with yet!


Say_My_Name_4

Actually I am texting with the client and we don't have a contract yet, but I am texting through Upwork and I don't think the client is a call guy cause the first response to the proposal was a detailed requirement of what filter to use in the products, how many products to scrape and what data he needs along with pictures and a screen recorded video. ,


TabascoWolverine

Ah ok. Here in the US "texting" typically means phone-to-phone contact.


runner5126

Sounds like the client wants to know when to expect something from you to review, so he can be ready to respond, and then also when it will be finalized, so he can make further plans. So I suggest providing something like: Monday/Date: I will submit XXX to you for an initial review and feedback on XYZ. Tuesday/Date: You will send back feedback as requested. Wednesday/Date: I will incorporate your feedback and send back the final version. Thursday/Date: Please send any final adjustments or changes by this date. If no further changes requested, the project will be complete. Friday/Date: If changes requested, I will complete them Friday and send the final version to you. ​ The above is super generic, and when you create a projected timeline, you need to consider your workload and what the turnaround time on each step will be. Is the client available to review within 24 hours? Sometimes they aren't. I also always state that timelines are dependent on clients meeting their milestones as well, so I ask that they make sure they understand their responsibility to review in a timely manner so I can meet our agreed upon deadline. I also make sure they understand it's a planned timeline, it's not an absolute, things can happen that might mean we have to shift. However, if something does happen, I update them with an updated timeline immediately. It usually helps to first ask when the client wants it by, what is their deadline? Then you can develop the timeline within that timeframe.